teacup50

65 ms·

631.
by teacup50 12y ago
Uh, when did that happen? It's slow, it's complex, it's a terrible solution, it's barely seen any uptake and near zero interest from tool vendors. Oh, and it's objectively, demonstrably inefficient. This is just ano
632.
by teacup50 12y ago
Are you serious? You're measuring complexity by header file count? I'm sorry, but that's small. By that ridiculous metric, I have numerous projects that have involved a few man months of effort that far exceed '66 header
633.
by teacup50 12y ago
> implementation problems of current generation JS Wake me up when you get to be end of the rainbow and find the pot of JavaScript gold supposedly waiting there.
634.
by teacup50 12y ago
No, and if you think that's what getting NaCL running will take, it explains a lot about the quality of Mozilla's technical output. First, the NaCL runtime and tools are NOT tied to Pepper. You could take those as-is and have the
635.
by teacup50 12y ago
NaCL is open source, the papers and documentation are all open, the build tools are all open. The only thing it's not is standardized -- and that's not Google's fault. Apple and MS are vested in their platform plays, and Mozi
636.
by teacup50 12y ago
What we really need is an open, standard hardware platform, not a browser based mobile OS that creates a closed consumer platform anyway. With browser OSs, the vendor can target the native platform, and app developers are stuck with secon
637.
by teacup50 12y ago
Who cares about binary firmware blobs? How is that any different than device firmware burned into an EEPROM, written to flash, etched into ROM, etc? Hardware is full of software. The line you create in the sand is arbitrary.
638.
by teacup50 12y ago
You seem to not understand that Apple defines the platform; consistency has to start somewhere, and it's not going to emerge by committee. Apple and 3rd-party developers extends conventions by exploring coherent and consistent exte
639.
by teacup50 12y ago
If you're ignorant to the degree that you don't understand how exceptions are part of the function's return type, it has nothing to do with my imagination.
640.
by teacup50 12y ago
Design that doesn't put the user first is egotistical by nature. There's nothing to get used to; design isn't new on Apple's platforms. If anything, Apple has driven software design more than any other platform or comp
641.
by teacup50 12y ago
You rely on human validation of your code's return type values via unchecked exceptions, and don't understand why your code is resultantly ambiguously defined.
642.
by teacup50 12y ago
No, I'm saying it's not possible to write reliable and correct code in C# using exceptions without also doing all the heavy lifting of the compiler. You can also write reliable and correct code in dynamically typed languages, wh
643.
by teacup50 12y ago
It has nothing to do with a "gold standard", or "just because Apple does it". It also has nothing to do with Safari , or using an application solely written by Apple. On the platform, we contribute to the ecosystem by r
644.
by teacup50 12y ago
Unfortunately, you'll lower the total value of the ecosystem by producing code and advocating practices that lower the level of reliability and correctness of code -- so agreeing to disagree doesn't really solve the issue that you
645.
by teacup50 12y ago
In this case, the decision is arrogantly wrong because it's predicated on an over-inflated sense of Firefox's position relative to the entire platform and ecosystem of consistent applications , and this position is based on se
646.
by teacup50 12y ago
The only failed language experiment are exceptions themselves. I don't use Java APIs that don't throw checked exceptions; if your code does that, I won't even consider working at your place of business, because that means you
647.
by teacup50 12y ago
No, Erlang has been writing fault-tolerant code with an explicit functional, immutable design, with very explicit semantics for defining process supervision and restart at every point in the heirarchy. That's not "catch-what-y
648.
by teacup50 12y ago
That's not what I want. I don't use the other operating systems, and I don't care if Firefox is consistent across them. You care if Firefox is consistent, and that's just arrogance, because you are not the platfo
649.
by teacup50 12y ago
That doesn't make any sense. Defensive coding means not silently discarding errors (by returning null, in this case), and has nothing at all to do with exceptions. As for rewrapping errors, yes, each subsystem should have its own error
650.
by teacup50 12y ago
"only catch what you can handle" is incredible nonsense. Your code is the only code that knows how the code it's calling might fail -- it MUST catch all exceptions and either handle them, or re-raise them with a well defined
651.
by teacup50 12y ago
Your arguments aren't supported by the facts: 1. It's not tied to V8. It uses V8 currently, but: - The vast majority of the code has nothing to do with JS. - Almost all of the JS-related PDF code is independent of V8. - The use
652.
by teacup50 12y ago
That requires a great deal more planning and time.
653.
by teacup50 12y ago
How does that take away any of your rights, though? The BSD licensed song still exists.
654.
by teacup50 12y ago
Literacy is not the same thing as the ability and interest necessary to write a novel.
655.
by teacup50 12y ago
I hope you can see the irony of your position when you're talking about the Linux kernel.
656.
by teacup50 12y ago
That's the dumbest definition of "user consent" I've ever heard.
657.
by teacup50 12y ago
Is 100K mps on 8 cores considered high for node/websockets microbenchmarking of the socket path? That doesn't seem like much from past experience writing high-throughput messaging code, and all this is doing is spitting out leng
658.
by teacup50 12y ago
How is contacting a server, unnecessarily and without user's informed consent or even knowledge, considered asking ?
659.
by teacup50 12y ago
As I said, anyone polite asks , and many don't do it at all.
660.
by teacup50 12y ago
Mostly the VC-backed web stuff, where folks coming from the web don't seem to understand that explicitly and unnecessarily contacting a server to push analytics is very different than recording the requests that web browsers make by

More ›