987 karma · joined March 2, 2013
I suppose you're not doing live type feedback? Given a test suite for the code being edited, that would seem like a natural thing to do.
The fact that application X is "just a text editor" is not a justification for X having poor editing functions. In fact, you'd expect a specialized text editor to have better editing functions that an IDE, since an IDE can have other selling points, such as an integrated build system, a version manager, a profiler or a debugger, whereas an editor can only impress you solely by its usability for...well, editing.
Unless he's a genetic mosaic, also known as the "reality is hard to squeeze into our all too simplistic data model" problem.
You meant that a linear type system is a total game changes. Unique_ptrs are an ugly hack to emulate a linear type system in an inadequate language.
That sounds a lot like transactional schema updates in Firebird to me. Plus being careful about how the app handles the data. Schema updates in Firebird are essentially instantaneous, with the row updates performed lazily (although if you need it, a SELECT COUNT(*) will force an update of all rows immediately).
I'd be surprised, because western media is exactly from where I found out about this two years ago or so:
http://www.nytimes.com/2010/08/15/world/asia/15japan.html?_r...
(...and a few others.)
That's because math always "goes straight to the point". There's nothing but the raw substance in it.
I don't think that should come as a surprise to anyone. In the long run, language-oriented approach seems to be the best approach to handling the intricacies of complex software systems. The only thing stopping it seems to be a certain lack of skills and experience on part of most developers, and the inadequacy of current language-building tools. (By any chance, are you familiar with the "let's simplify language construction"-related work of people at vpri.org?)
Of course it is safe. You have at least two options: software sandboxing (NaCl, Vx32, OS-based sandboxing...) or proof-carrying typed assembly. Of course, the first option is complicated by the horrible state of the most prevalent hardware architecture available today, but that's something to be fixed in the future anyway.
"irrelevant in the age of multi GHz CPUs in your phone"
Oh, thank you very much. You're perpetuating the trend of "What Andy giveth, Bill taketh away" with this kind of thinking.
"native platforms have bugs too"
And studies confirm that the amount of bugs is largely proportional to the LOCs. The web-based approach, however adds a few million lines of code to something that would have, say, tens of thousands at most on its own.
That was primarily because the previous regime was terribly bad, not because the new one was terribly good.
I happen to have a Parker Vector, but many people swear by the price/performance ratio of Pilot 78G. (I believe it's 78G, it's something-G anyway.) It's cheap, go ahead and try it. And keep in mind that Japanese nibs are finer than the designation (F, M...) would suggest.
You can also do it in stream-based or data-flow-based languages. Or in pretty much any DSL you decide to implement, if the semantics of the language itself is reasonable.
You can get sued for anything, but the court will throw it out if the civil case is unfounded. I don't know how you have it in Poland, but the Czech copyright act stipulates that private copies ("copies for sole personal use") of everything except software and "electronic databases" (telephone directories etc.) are completely outside the purview of copyright protection, up to and including the disregard for the legality of the source of the copy (confirmed by a verdict of the Supreme Court in 2006) If something similar is the case in Poland, what basis could a civil case possibly have?
Well, it's still the language from the year 1980. The very fact that you judge a 1980-vintage system as "not bad" compared to existing alternatives is telling in itself. Alan is working on a 2010 version even as we speak. :-)