Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
unscaled
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
80 ms
·
661.
▲
by
unscaled
11y ago
Globally, yes. I think parent was talking about the US market where OS X is slightly more prominent and according to StatatsCounter surpasses the market share of Windows XP and Windows 10 combined. Microsoft still controls 3/4 of the d
662.
▲
by
unscaled
11y ago
I'm pretty sure there was no direct malice here (except for the usual Apple disregard for 3rd party components), but the security reasoning behind this move is still questionable. The only danger of a compromised Touch ID sensor, is th
663.
▲
by
unscaled
11y ago
It's about time they did. I always wondered why this was disabled by default.
664.
▲
by
unscaled
11y ago
If someone has told you synchronous I/O is slow, they've obviously misunderstood the entire C10k argument going on for a while. The problem with synchronous I/O is not speed, but blocking. Blocking means the only possible con
665.
▲
by
unscaled
11y ago
Nginx implementation may have changed since the last time I delved into it (and I delved pretty deep), but at least 2 years ago that was not the case. Nginx did have some vestiges of an abandoned multi-threaded implementation attempt from t
666.
▲
by
unscaled
11y ago
You make a very important point here. When you're creating a very high-throughput network server, you want to use as little Reactor and proactor I/O makes it very easy to reason about execution order and more importantly memory u
667.
▲
by
unscaled
11y ago
>That will keep the market flooded with artificially cheap Sharp products -- mobile phones, solar panels, air conditioners, printers, microwave ovens Besides, as a domestic consumer, sharp products are not necessarily cheaper than compet
668.
▲
by
unscaled
11y ago
When I was there the roads were almost devoid of cars. They've also just opened their first ATM. Things can change a lot in 10 years. :)
669.
▲
by
unscaled
11y ago
You've said most of your build time was linking, so wouldn't you get the same build times with C? Templates would slow your build time a lot though, so they come with a price. C++ would never beat C on build times, but C never cam
670.
▲
by
unscaled
11y ago
I was positively surprised by the constructiveness of the article itself. You'd usually get Linus' style rant about how C++ sucks so bad and C is the epitome of simplicity and design. I wholeheartedly agree with you that both lang
671.
▲
by
unscaled
11y ago
Oh, if it was only so easy! There are many other languages which abound with incompetent programmers. Even an atrociously simple languages had many incompetent programmers over the years. On the other hand, there don't seem to be a lot
672.
▲
by
unscaled
11y ago
It's worth noting this was written by a different author.
673.
▲
by
unscaled
11y ago
Hey, C came earlier and strcat is still in the standard, as well as non-prototyped function calls. Someone told me FORTRAN still maintains backward compatibility with arithmetic ifs, and it's been like, what, 60 years? Strange that.
674.
▲
by
unscaled
11y ago
I agree with you that C++ streams are rather horrible. This is probably the oldest part of the standard library and the original design predated both templates and exceptions, so it had to do with virtual functions and error states. I wish
675.
▲
by
unscaled
11y ago
It's not blaming someone else. Bjarne worked at AT&T Bell Labs, and once C++ caught management's eye and became more than his own personal project, 100% compatibility with C++ was a business requirement. Bjarne ended down expa
676.
▲
by
unscaled
11y ago
I find it the other way around. It's usually C hackers who tend to describe C++ as the devil incarnate. C++ developers tend to be more pragmatic - we'd happily write in C if necessary, we just find it limited. And since C++ is alm
677.
▲
by
unscaled
11y ago
I've never really got the "C++ dialects" argument so popular with C enthusiasts. Sure, C++ is several order of magnitudes more complex than C, and this complexity breeds different dialects. But for an experienced C++ programm
678.
▲
by
unscaled
11y ago
More likely, someone who hasn't programmed C++ in the last 10 years. Forgetting auto, and using the cumbersome 3-part for loop with iterator boilerplate when you only need value shows age. Initializing the list is also easier now, with
679.
▲
by
unscaled
11y ago
Not it didn't. The work on Qt standard on 1991, according to Wikipedia. The work on STL only started in 1994 and became a standard with C++98, and even then it took time for compilers to get decent standard support. So every library ne
680.
▲
by
unscaled
11y ago
Yes, GLib basically implements its own full-fledged OOP system on top of C. At which point, you start asking yourself, why are you not using C++? In my experience, most of the people who say they don't need OOP or generics end up imple
681.
▲
by
unscaled
11y ago
D is also primarily garbage collected. You had an option to create scoped classes (allocated on stack) but it's apparently deprecated now. I think Swift would be a better example here. Or objective C with ARC.
682.
▲
by
unscaled
11y ago
So let's stop unit testing all of our code, since it's provably incorrect anyways, due to cosmic rays flipping random bits of RAM once in every gazillion calculations.
683.
▲
by
unscaled
11y ago
> Although developers skipping return value checks is true in most languages. Yes, which is why I disagree with Go's approach for error codes as return values. I'm not saying that exceptions are the right solution everywhere, b
684.
▲
by
unscaled
11y ago
As a C++ programmer who delved deeply into nginx, I think that your chosen example of "high quality C code" is telling of the state of C programs. It could be one of the best specimens of C code in terms of organization, but absol
685.
▲
by
unscaled
11y ago
That's harsh, but probably true. There might have been good reason to make null-terminated strings the default in the past (e.g. K&R C not passing structs by value), but it has little meaning today. The arguable memory overhead of
686.
▲
by
unscaled
11y ago
1) Memory safety is practically zero-cost in languages like C++ or rust if you disable runtime bounds-checking (which the C++ standard library does by default). You don't get 100% safety, but it's still leaps and bounds better tha
687.
▲
by
unscaled
11y ago
Properly executed RAII, at least in C++, should never break in the two cases you mention. The RAAI object should be non-copyable (no copy constructor in C++), so the only way it can be passed by value to a closure is with an explicit move o
688.
▲
by
unscaled
11y ago
Did I ever said snap is dumbed down? Read my post again. I said it would get the undeserved reputation of being "dumber" than "real programming". Did I ever say Logo was unsuccessful? It was at the very least tremendousl
689.
▲
by
unscaled
11y ago
I think you're exaggerating on both counts. While rental Wi-Fi in Seoul was cheaper and more reliable (at least last time I was there), broadband in Tokyo is definitely better than America. I may be wrong, but FLETS (NTT's FTTH&#x
690.
▲
by
unscaled
11y ago
I like the idea of visual programming as a way of making introductory programming classes more engaging and draw kids into programming. But it's definitely not a new concept, and many kids in previous generations have had LOGO classes.
More ›