Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Only need TWO (Score 1) 272

They probably only need just TWO employees, a CEO to get the money, and a secretary to collect it.

Every single action Microsoft makes is met with incessant criticism. This makes a lot of sense as for two decades the Microsoft marketing machine has firmly established this universal notion that anything different than Windows is scary, different, and OMG, *incompatible*. That worked very so well as no Windows user wants anything different than what they have right now.

So, all Microsoft should do is just keep printing copies of Windows XP, since that what everyone wants, and just keep collecting the money. Users would be a LOT happier as they would never have to worry about any change, and the CEO would be happy as he can just keep collecting the money with no effort.

Comment Emacs (Score 2) 359

I use Emacs and

1: C++, C, Objective-C
2: LaTeX
3: Python
4: Bash
5: Text files

I used to use (also in Emacs):
1: Java
2: C#
3: Fortran

Emacs works for just about any language out there, I use variety of languages and a variety of different platforms, Emacs is the same on all of them and just works. 2:

Comment VIM (Score 2) 359

Just a question. Is there anyone out there younger than around 40 who uses VIM because of their own choice? By that I mean, they at first turned on a Unix/Linux box, investigated some editors and chose VIM. Nearly everyone I know who uses VIM uses it because someone else originally made them use it and they stuck with it. I know this sounds like flamebait, but seriously, its an honest question.
It just seems like Emacs is a lot easier to learn because it one keystroke to get to a menu, and just another to get to a help system.

Comment Re:Uh, sure.. (Score 1) 359

WHAT!?!?!

Apple is probably the king of the designated editor group, with microsoft coming in at a close second. These are relatively closed stacks and have purpose built (and pretty decent) tools to work with them, so most people do

If anything, Windows is the absolute king of languages that CAN ONLY BE USED IN THIER IDE. Take a look at Visual Basic, completely tied the VB mouse clicky clicky IDE, then of course there used to be a company called Borland which also made mouse clicky clicky languages like Delphi, a variant of Pascal that was locked to an IDE, I think they also tried to do the same with a version of C++. Then of course, there was Microsoft MFC which was so bad that that they had to write an IDE to even use it.

Comment Re: It's too slow. (Score 1) 254

Once the app is up, if done right, performance can be decent for most things, pretty comparable to C++. The big thing is once it's up. The REAL killer of any c#/.net app (or any env that requires a VM like Java) is the load times. Even tiny c# apps take forever to load. So I would really recommend c++. I know if you really wanted you can do cross platform with mono but it's a lot easier with c++, especially if you use a framework like SDL.

Comment Re:what's the point anymore (Score 1) 113

Wrong. If Unisys mainframes are anything like IBM s390, then almost everything is written in assembler. So, unless they have a whole hardware translation / emulation layer, you can't just re-compile. Going to a new processor architecture if everything is written in assembler, its much easier just to throw everything out and re-start.

Comment Re:There is something called multi-process you kno (Score 1) 196

Of course I know about multiprocessing. Why have one copy of the interpreter and libraries loaded when you can have N, plus its so much more efficient to marshal data across process boundaries than to access a global shared memory block.

I've heard this processes are so much better because we can't do threads for so long. Kind of like if I cut off my right arm, its so much better to only have a left arm because you only need to move 5 fingers instead of 10.

Comment Re:And it still has the GIL (Score 1) 196

2. The only reason it's hard to fix is because certain parts of Python are overly dynamic. Since they broke backwards compatibility in Python 3 it would have been the perfect time to fix it. Instead they broke backwards compatibility for stuff 99% of the community doesn't give a fuck about and now nobody is upgrading even though Python 3 has been out for over 5 years.

That is really insightful, seriously. Python 3 did break backwards computability, this really would have been the time to fix some original design flaws, but they didn't, instead, they focused on stuff, like you said 99% of the people out there don't care about, hence why so many use 2.7 today and how many new projects are even started with 2.7.

There's nothing wrong with design flaws, we all make them, you just at some point have to go back and realize you made a mistake and fix it.

Slashdot Top Deals

There are two ways to write error-free programs; only the third one works.

Working...