Comment Re:Vodka (Score 1) 770
Windows
Windows
> Apple basically invented the home computer
That's rich
They revolutionized the home computer with a GUI interface model stolen from Xerox, they lowered the price of the hardware (Woz was a wizard after all), but they haven't invented it.
The first home computer intended for consumers was from Altair - aprox. one year before Apple I was released. And the credits for the "home computer" as it is today cannot be attributed to a single individual or company. Far from it.
But then I guess it's fashionable to credit ol' mighty Steve for everything that's shiny.
Because the manufacturer of the related hardware isn't the one that's a threat to Nokia. Apple is.
They are designing the iPhone, they are the ones getting most of the profit.
People are calling Nokia a patent-troll, but Apple deserves this. They have patents on multi-touch gestures and because of that competitors (like Android) can't implement features requiring multi-touch.
Want a free pass? Learn to play nice then.
Dude, I'm really sorry about those poor bastards who died in the second congo war, but come on, is it the same as millions of people dying everywhere on this planet, with forests and cities burnt all over the place, all the world living in constant fear, asking yourself if you're house is going to be hit by a house tonight
That's the coldest argument I've seen in a while. You want to be part of a war, to fight? Go for it, nothing stops you.
And seriously
You could even turn it around and say that the number of 3rd party frameworks being developed indicates the language is missing some important stuff and everybody is trying to solve it in their own way, with lots of redundant, very similar frameworks.
No you can't
If a platform doesn't have redundant libraries, then it's either not popular, or it is tightly controlled.
AOT compiling has nothing to do with having a runtime or a garbage-collector. AOT refers to code being translated directly in machine code, instead of an intermediate byte-code language. When you're using an intermediate language you can do neat tricks like generating and manipulating the code at runtime, and that's why JIT-ing is disallowed.
For a garbage collector to run, you have to keep some state at runtime, like a global count of the number of references an object has or local counts of references (on each object) to construct a graph of objects that are still in use, but that's not code evaluation at runtime.
There will be disadvantages of Mono on top of the iPhone though. Because JIT-ing and eval-ing are forbidden, you can't use libraries that rely on runtime bytecode manipulation.
I doubt they'd have a problem of approval. There are already games developed with Unity3D (http://unity3d.com/), which is a toolkit for iPhone games running on top of Mono.
Using C# may not be much better, but learning yet another programming language, that's just another variant of C, with its own libraries and ways of handling events and with its own tools
Yes but crappy applications come along with increased popularity.
The quality is high on the iTunes Store compared to the crappy Java apps we are used to, but that's only because the iPhone has been a luxury for people with money (and the hardware specs are also higher than your average Java-enabled phone). But now that it's growing in popularity you can already see how the average quality is going down fast.
Your argument is also the same elitist bullshit "raise the bar to entry to raise the quality" -type I've heard countless times before. Well, guess what, the people in PHP/Basic/Delphi/Java communities (although I hate them all) have given birth to some of the best applications around (being more results-oriented, rather then being clever).
Linux may represent a single digit in their desktop marketshare, but on mobile phones the market share of Linux is a double-digit.
And on servers
I wouldn't underestimate Linux/BSD if I were in their shoes, and I don't think they are. You can't beat a zero-price tag, and while some people say Windows is easier to administer (beating a dead horse on ROI), that's not my experience. YMMV
And Red Hat and Crosover Office really don't make money at all... It is all a myth.
I know you're being sarcastic, but what about Loki Games?
Also because of Qt's design, I barely have to bother with memory management in my GUI apps. So far I'm averaging one delete statement per 1000 lines of code.
Yeah, but you have to miss just one of those deletes, and boom, you've got yourself a memory leak.
Using Qt I can do all the things you mentioned and just about everything else in the C# and Java class libraries.
Not everything is in Qt. And when you'll want to import other libraries in your code, then you've got yourself a shiny new string library to convert back and forth to QString, and a shiny new hashmap that you'll convert back and fort to QDict.
1) High performance VM
When measuring performance, the standard deviation is more important than the average.
The JVM may have lots of performance, but it boots up slowly, it warms up slowly, and when the garbage collector kicks in the world gets frozen.
The CLR may not have such a fancy VM, but its main language (C#) is more efficient on current hardware (structs are allocated on the stack, methods are non-virtual by default), while being better designed.
2) Code that does what it says without hidden conversions, text substitutions, and macros.
This implies that explicit code an 8 year old can read is somehow better. That's not always the case.
One way to tackle complexity is to build layers of abstractions. For a positive example you only need to look at mathematics
And another thing
3) Other languages that are actually useful like Scala and Clojure.
F# is an Ocaml clone, and I saw a lot of Ocaml libraries being ported to F#. It also has good VS integration and good tools.
Axum is a language with actor-based concurrency, much like Erlang. It's still experimental, but I've played with it, and it's already solid.
And then there's the DLR which is a framework of optimizations for new languages and a MOP making dynamic languages interop better
I know of an open-source effort for Java, similar to the DLR, but if it doesn't get adopted as a standard among language designers, then it's all in vain.
Also,
And LINQ? Why are you doing database and 'data sources' queries in something like C#?
You misunderstood LINQ. It is a generic framework for doing interrogations on any kind of collections. Being able to query databases and XML objects is just a side-effect of its design.
And it's really useful too. If you look at any piece of code you wrote, chances are you're looking for some kind of object in some kind of connection or data store. Linq gives you type-safety, a C# syntax for queries (with C# methods and types) and a unified language for interrogations on structured data (instead of having to use SQL (specific to your rdbms), XPath and iterate through arrays, all in the same method
This seems to me that you're just sorrow because the grapes are out of reach.
I'm not aware of any proof on the contrary.
You can pick any related story about VFAT you want, it still doesn't say anything about Mono.
What would stop them? How about a dozen other companies with similar patent portfolios?
Gnotes is just a fork, line by line, done with the sole purpose of replacing Tomboy, worked on by one individual that's on some kind of a holly quest.
Not to mention that Gnote's license is GPL3, and porting features back in Tomboy (assuming there will ever be features worth porting) is currently not possible.
Tomboy, although it's "just a post-it" application, it does have usefulness and innovation in it.
Of course the Tomboy devs are annoyed. I would be too.
> If I use MS source code, I am required to release my code to Microsoft under their control and copyright
You're picking on a non-issue
That's not the case with GPL. Surely using LGPL is a lot more reasonable
But I don't think the OSI open-source definition should allow for GPL
A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson