newt0311

33 ms·

421.
by newt0311 18y ago
mostly correct but very much incomplete. No discussion of the dihedral groups, hamiltonian groups, stabilizers, kernels, group actions, etc... The rubics cube solution at the end is interesting though.
422.
by newt0311 18y ago
Should probably still include that no warranty clause somewhere...
423.
by newt0311 18y ago
Its interesting because it breaks with the normal paradigm of lexically scoped variables. It is an exception, something that imho should be removed as quickly as possible. Just because some behavior is documented does not imply that it is w
424.
FCC encrochment of the internet.(online.wsj.com)
1 points by newt0311 18y ago|0 comments
425.
by newt0311 18y ago
Points 1-4 seem fine. Furthermore, I should point out that if you consider recent benchmarks, the bottleneck was not the DB but the framework on top (ie. Django or ROR). Generally DBs are extremely well designed. Furthermore, it is still po
426.
by newt0311 18y ago
"necessary" is always in relation to a preferred outcome. In your usage, this happens to be optimal economic performance when it comes to ISP. Now, first of, note that government interference int the ISP business does not in any way guarant
427.
by newt0311 18y ago
Is BT throtteling bad? Maybe. Do I want the FCC to regulate it? Definitely not. If the US govt. wants to crack down on ISPs this way, I would prefer that they at least do it through congress. Giving government more power is in general a bad
428.
by newt0311 18y ago
umm. Not charging state sales tax for online websites is usually legal as they are across state lines and states have no power to tax beyond their borders. This has already been well documented in several supreme court decisions. So no, I a
429.
by newt0311 18y ago
No. I have to say, I agree with the BDFL here. Tuple unpacking in function headers is prone to bugs and can lead to ambiguous behaviour. It also doesn't fit very well with other features like keyword arguments. You are right that the extra
430.
by newt0311 18y ago
be wary of tuple unpacking inside function headers. PEP 3113 removes it from python 3000. See http://www.python.org/dev/peps/pep-3113/ for more details.
431.
by newt0311 18y ago
Interesting concern: What if some malicious hacker breaks the anti-theft system and starts sending it arbitrary commands? Just a thought. Still, very nice idea.
432.
by newt0311 18y ago
Actually no. Take lisp for example. It's syntax can be described in a few lines. The functions also are usually quite straight forward and its pretty easy to go back to previous code. Or try python. This language is also pretty easy to work
433.
by newt0311 18y ago
Excellent article. One of the clearest explanation of how to use unicode in python that I have seen yet.
434.
by newt0311 18y ago
story of my life.
435.
by newt0311 18y ago
kewl.
436.
by newt0311 18y ago
I remember reading something like this somewhere. It goes along the following lines: The only good thing about MS Win. are the ubiquitous driver support and secondly their programming API (since 90% of the desktop code + office + ... etc...
437.
by newt0311 18y ago
No, because normal transactions shouldn't be taxed either. At least not as heavily as they are now. Electronic transactions happen to be one of the few parts of the system that actually work.
438.
by newt0311 18y ago
Or... we could use reiser4. The design of reiser4 was inherently geared towards making DBs obsolete. Hans may have failed as a person but he was still a great programmer.
439.
by newt0311 18y ago
I am sure that you are not the only one who requires such an application. Regardless, that is not a database (certainly not a relational/SQL one), it is effectively a dumb object store. I meant nothing derogatory when I pointed out that dri
440.
by newt0311 18y ago
Umm... Supply and demand works... Not much in the way of news.
441.
by newt0311 18y ago
From earlier news: No views, no stored procedures, no prepared statements, trigger, and who knows what else. Seriously, THIS IS NOT A DATABASE.
442.
by newt0311 18y ago
Correction: Nifty unnecessary hack. Why not just write a function which returns another function that performs the SQL statement? That is almost but not quite exactly what the decorators do and it would accomplish exactly the same goal wi
443.
by newt0311 18y ago
agreed. This is a massive misuse of decorators.
444.
by newt0311 18y ago
"it has nowhere near as many edge cases as C++ or Perl." Understand that comparing to Perl and C++ for syntax is like comparing some smell to that of rotten eggs. If you would like to compare syntax, use LISP or Python or for functional lan
445.
by newt0311 18y ago
Actually no. PostgreSQL and MySQL are certainly not neck to neck especially in performance. See http://tweakers.net/reviews/657 Summary: MySQL comes close to beating PostgreSQL (in speed) when there is little contention but gets absolutel
446.
by newt0311 18y ago
I disagree. Code without comments will never be as understandable as code with comments. This is true because code is designed partly for computers while comments can be written entirely for humans. This is important because comments only h
447.
by newt0311 18y ago
"Today’s web apps are generally written with frameworks like Ruby on Rails, Django and the like, all of which include things like sanitized database queries and more. So bother with prepared statements or other expensive (performance-wise)
448.
by newt0311 18y ago
Whatever the reasons, good for him (and it is very likely that he already owns some equity so he gains even if xobni gets bought out later though not so much).
449.
by newt0311 18y ago
"Stored Procedures, Views, Triggers, Query Cache, and Prepared Statements are gone for now." Its fine if they do this but why are they still calling this a database? Its a dumb object store (not that that is a bad thing). The term RDBMS has
450.
by newt0311 18y ago
So... The compiler itself is insanely efficient (I have heard that it is on the order of ~200 bytes). However, the compiled code is probably nowhere near as efficient simply because the high level constructs are hidden from the compiler. Fu

More ›