skysight-inc/HackerNews huggingface dataset:
> main issue is probably lack of IPv6 anycast support (??)

It requires root or user-namespace shenanigans to assign the v6 address needed by the p2p client.

And access to BGP tables.

And they don't estimate how long such a bootstrap process would take, since for small networks it would potentially have to scan millions of candidate addresses.
Both US and Luxembourg have laws stating that if you get there first you own it and can use it for commercial purposes.
Loved the blog post. Too many people just love jumping the gun and saying that C/C++ are fast languages. I believe it was Chandler Carruth who said that C/C++ aren't performance languages, but rather languages that give you the largest control of your performance.
It would be interesting if there were something similar to real estate tax, where you get charged yearly based on market value.
> I keep trying to get people to not use C++ for these but funny it's almost a trend now.

I can understand why L4 choose C++ at the time, as it had stricter checking than C, but OS kernels have very little internal code reuse that necessitates inheritance or templates. This is doubly true of microkernels. There is literally no reason to use C++ in this domain. Ada or C, and soon Rust should be the only considerations IMO.
I believe modern C/C++ has the restrict keyword which tells the compiler that pointers don't overlap. I'm not sure if this applies to arrays, but if so, it should be fairly trivial for a compiler to optimise parallel execution so that it matches Fortran or OCaml.

What am I missing?
Hunting the Truth in a Paris Ghetto
That means "Comes from company that made popular IDE so it has lots of marketing advantages".
I have to side with the parent poster. The state essentially subsidized the "rentiers". I don't see how this is different from former communist countries doling out lucrative enterprises to private individuals. You might say what was done in capitalist countries (i.e. insane regime of low interests/hidden debasement of currency) wasn't corrupt because of free markets. I call BS on this. A poor person does not have access to said markets (downpayments are the hurdle). Take Toronto as an example. Pretty much most people who bought detached houses prior to 2005 are millionaires. The rich people at the time bought a bunch of houses. How is this not a gift from the state? If you happen to be a schmuck who came in later on or have poor parents, well ... sorry ... that's the way it is.
My take is that comma separated JSON could come in handy

(1) when dealing with huge data volumes when streaming is needed or memory restrictions apply or

(2) when CSV does not work because there is no common standards on how to deal with special characters, empty lines and the like.

But then, in case (2) I could also just use JSON if the set is not too big. So, that really leaves (1) as the most important use case. Or did I get this wrong?
React and Flux – An Introduction (plus some abstract thoughts on UI’s and trees)
> It's weird that languages with unpredictable runtime characteristics such as Java and C# are being advertised as systems programming languages.

Languages don't have unpredictable runtime characteristics, only specific language runtimes have unpredictable language characteristics. One could replace the standard .NET runtime GC with a hard realtime GC, and .NET would then have more predictable runtime characteristics than C and C++.
I wouldn't design any system to be crufty or have bugs. I was just pointing out that it happens. And honestly probably gives us a lot cooler stuff than were software production restricted to developers who were certified to produce best practices code.

I feel like without weird blood we'd only ever get enterprise-approved spreadsheet software.

PS: Caveat. Personally, of course I'd never use stuff like that for mission critical deployments until it's been battle tested.
"People are more willing to share an article than read it"

Of course, Hacker News is an exception.
> So these things (PWM, ADC) are "standard" to all embedded systems?

Not really. PWM is more common (and "can" be done in SW or using other tricks if needed)
> This function is painfully short.

Irrelevant. Other functions are longer. And needless human minification will undoubtedly creep in there too.

> What, exactly, is this inconsistent with?

Other functions.

> expressing frustration frankly.

Calling someone a wanker isn't exactly a pinnacle of expression.
I like to build something that I've programmed before in another language. Maybe this seems redundant. But if you have the problem fresh in your mind, it leads to asking the kinds of (Googleable) questions that get you very quickly to a base-level understanding of the new language. It also sheds light on the areas where the language is better/worse at specific things than the lang you are used to working with.
> With GC languages you don't have any - the GC will kick in unpredictably.

This is only true of specific GC implementations. Incremental GCs never pause the program. On-the-fly and realtime GCs pause the program for a few microseconds.
One answer to that question, which I have bookmarked: http://blog.fogus.me/2009/05/29/pet-projects/

· Lisp interpreter

· Lexer generator

· Knuth's Pac-Land

· Linear Algebra library

· Workflow engine

· m-ary tree

· Now Do This app

· Project Scaffolding generator

· Gap buffer
Best language for image processing
Hi All.
I start new project for image processing like (detect face, check image is same other image...). So what best of language can i choose.
Thank you so much.
Yes, but home prices are not. If they were, my guess is we'd see a different story (especially regionally). Someone used to do a shadow inflation index .. when energy prices were excluded from the numbers. Forget the details.
The well-known microcontrollers do have both built-in - Arduino and MSP430 are two of the popular ones.
How Publishing White Papers Can Increase Your Revenue by 2500 Percent
Are you implying this comes close to the convenience of LastPass?
I don't know for sure hence the question mark :)
What I know that Carbon 14 which is used for carbon dating is a cosmogenic isotope which is created when high energy cosmic rays hit carbon atoms in the atmosphere and in other places.
Nuclear tests release radiation which created much more carbon 14 than what was created with the natural process of absorbing cosmic rays.

I'm not sure what's the current source of carbon for steel, I don't think it's coal it was always too impure and contain allot of contaminants especially sulfur, and I that high end crucible and powdered metal steels are made with considerably more pure and precise sources of carbon, from wikipedia it seems that the source of carbon for modern steel is charcoal (which is affected by C14 imbalance) and coke (which i have no clue if it's affected by post nuclear blast radioisotopes or not) which is refined coal but this only references to modern steel (late 17th century onwards, and I'm not sure what is used today).
Help?

I have no idea WTF is going on here. I've tried to search around for a clue but the more I read the more confusing it gets.

At first it seemed that Ethereum was a kind of cryptocurrency like bitcoin (something that people could "mine" and exchange), then something about "contracts" that don't require trust, then something about it being effectively "a computer" that never stops, an investment system investing in something no one ever actually names, some story about a hack that drains ether out of the system.

And now this story which has words like... "Governmental", "Rock-paper-scissors", "Casino", fees "stolen" because of constructor bug, "ponzi".

Even forgetting all the confusing jargon, I can't come up with a mental model that makes any sense at all. Is this just an elaborate puzzle game for geniuses? Or are people making and losing real money with this? By "money" I mean something that can be converted into actual US dollars right now and stored in a bank.
That's why smart contracts will be really lousy for things that traditional contracts are used for.

But on the other hand, there are some simple - yet important - things that can be implemented in smart contracts pretty easily. Say, futures, or stock options, or certain kinds of insurance. For these things smart contracts are great because they offer extremely cheap enforceability and speed.

This is a textbook blue ocean, or innovator's dilemma. The new tech is much worse than the old one in some cases (enforcing intent), but far better in some other ones (speed, enforceability, global access)
While I agree with the author about the main topic, the actual content does not illustrate the point well.

The author wrote a naive loop in a bunch of languages, and, got a faster result in OCaml (0.3 sec) than in C(0.8 sec). Right, but the code was a totally naive loop:

for (int i=0; i < 20000) { for (int j=0; j < 20000) { x[i][j] = y[i-2][j+1] * y[i+1][j-2]; } }

The fact that C has a bunch of libraries for vectorization of such code, or that there are million compiler directives that can speed that code a lot is somehow missing from the article.

So, the conclusion is that a compiled OCaml code is twice as fast as a naively written unoptimized loop in C.
Economically for the planet a carbon tax would make sense but individual countries may be better off pollution and letting others worry about the damage.

>Many large users of carbon resources in electricity generation, such as the United States, Russia, and China, are resisting carbon taxation. (Wikipedia)
For a personal project or for creating a new app from scratch where I am lead engineer, sure Kotlin would be an easy choice.

However, right now I am a senior engineer working on a 8 years old android app alongside 15 other Android devs.

The switch to another language is not even something that the current lead or the CTO are willing to consider.

In their defense, we would have to train the whole team, this would be a major task and build times are already a big issue so anything degrading them is hard to push for.

A push from Google would help a lot, it would remove a lot of objections like "this is hipster shit" or "I am not going to learn the language of the month" (coming from people who have not learned any language in years) and force them to take it seriously.

Even the iOS team barely use Swift though, so I don't see it in a near future.
I guess I just have to search for another company.

> our introduction to a largeish Android codebase has been a great success.
Do you mind sharing some details ?
And also may become obsolete after Java 8/9 (as Coffeescript after ES6/7). Problem is that noone in Java body shops ever touched Java 8, they're still migrating from Java 5 to Java 6.
I always end up rewriting Tetris and a basic MUD in whatever language I'm learning.
"Smooth Jazz" can die in a fire
True, the efficiency argument is wrong. Thinking about your algorithm and knowing where you actually need to be efficient are far more important.

What I appreciate about C in particular is that it seems harder to "program by accident" than it is in most languages. C was my first language. After I learned C, I programmed in a higher level language for a while later before discovering that its runtime threw exceptions on 'array subscript out of bounds.' I discovered it by looking over someone else's shoulder in a lab. I realized then that I had just learned not to do that because C was so unforgiving.

We can argue whether the kind of discipline of thought that you gain from that experience is good or even useful today, but I suspect it is. It's different from learning how to do mental math in a world full of calculators - that's just raw mental exercise.
The infographic and thus 80% of the content of the page exists, but my adblocker in Firefox suppresses it for example.
I am in that slack channel.

Do you have any adoption numbers though ? From what I see in the local companies, kotlin is still very rare, except for a couple of startups (which makes them very attractive tbh).
That anecdotal evidence of course and I would love to see a tide change but hard numbers would be an huge help.
Nope, that's pretty much exactly it. It's the one thing JSON struggles with and this seems a good aT to deal with it and in a way that's still quite user friendly
I store the original 2fa seed somewhere offline and safe (wallet, safe, etc) so that I can bootstrap a new auth device at will.
Slower I can understand, but I don't see how a C# interface could possibly be inherently more complicated than a C or C++ interface for something like an image library, at least to the extent you're implying.

Even hardware interfacing via memory mapped addresses would just need a small shim and types that are byte compatible with C structs you can call via P/invoke, isn't particularly complicated.

Can you give a specific example of what you're referring to?
There are also cases of people selling cars (and other stuff) ultra cheap on ebay, because they misplaced a comma when specifying a price.

It was obvious that the price was supposed to be $20k, not $20.000, and yet the seller lost.
- The adherents are international, and may prefer a standardized form of law accessible cheaply and easily to all

I think this is undervalued, and probably going to become even more important in the future. Largely because it's something that the current legal framework simply doesn't provide.

We have tenuous legal agreements between nation-states (largely of the "we choose to obey now because it's in our best interest" variety). And we have legal systems that apply in a single country. But we really don't have an ironclad anything in the ether (ha!) between those.
It also seems to have an option for an external power supply so you could potentially add more power to it.

I don't know what the specs for it are, but 1000mW is 20dBM which gives you a very nice coverage range on it's own and it's definitely possible to power that of USB alone.
Meanwhile, Toyota is allowed to ship buggy, untested, unauditable ECUs[0]. How can SE be considered a legitimate engineering discipline when such examples abound?

In the bad old days, steam boilers would blow up a lot; check your state and maybe local laws and you'll likely see a section to regulate this. Bridges were also prone to failing, and still do due to design errors: https://en.wikipedia.org/wiki/I-35W_Mississippi_River_bridge... (and even then, the bridge was sufficiently over-engineered that it lasted a long time before failure)

As for the EE examples you give, it just so happens I'm about to personally totally rewire a house I just bought that was built in 1910. Relevant things I've noticed include:

The National Electrical Code is drafted and revised in an open fashion, is thoroughly sane, and anyone can buy a copy. My city also makes copies available for free for perusal, and at the counter were you apply for permits and such there was a copy of the combined complete code for residential housing (1-3 stories, 1-2 or 3 families). That version is also online: http://publicecodes.cyberregs.com/icod/irc/2012/index.htm (that's one revision behind the current, many cities like mine prefer to not be at the bleeding edge).

Then there's the permitting and inspection process: while it's obviously ignored a lot, by law you're required to apply for a permit, including plans of what you propose to do. Upon approval, you post the permit at the work site, and call in city inspectors for "rough in" inspection(s), where they will check whatever will eventually be hidden, and they do a single final inspection when all is done. So there's enforcement of the code (at the very least backstopped by insurance companies who will look askance if your unpermitted work results in a loss), in a rather open way, and the city's top dog for this, the Building Official, certainly knew the electrical code when I asked him about the interpretation of one detail.

All car makers, by comparison ... well, there's not even a PE system for this field (https://www.nspe.org/resources/licensure/what-pe), it's too new, and and there's no consensus on even the most fundamental of things. Everything they do is in secret, with no outside oversight mechanisms, and one company we though really had their act together, such that we'd trust their code with our lives, turned out to be utterly unworthy of our trust, that is Toyoda, of course.

My take on this is that this sad state of affairs will continue until a software error kills 4-6 figures of people, and of course there are many domains of software where the rigor that's in theory demanded of embedded systems like cars isn't required. Like, say, this social media site we're using right now.
Total agreement. :)
Awesome!

I took a screen-shot, to help out the computationally challenged:

http://www.weegeeks.com/upload/a1studmuffin-daredevildave-sp...
as much as it's not part of the standard, __restrict__ allows limiting the effects of pointer aliasing in C/C++. [1]

[1] : https://en.wikipedia.org/wiki/Restrict
The post was published in 2006.

The claim that Fortran arrays are easier for the compiler to optimise than raw pointers in C/C++ may well be true. But I imagine that there has been progress on compiler technologies to address auto-vectorisation in C/C++ since the post was written (and since C99, C has the restrict keyword too). Can anyone comment?
That's right: the author wrote a bad argument because they made an invalid performance comparison: naive vs. sophisticated. Is there a C code that can be written that compiles to assembly which is as efficient (or more) than OCaml? Likely so, and if the author doesn't even attempt to do that, I don't find their argument convincing.

I recently learned that Knuth created a virtual instruction set (MMIX) specifically because he found that comparing algorithms with high level languages was too prone to problems. Using a direct instruction set that executes on a virtual machine means that algorithm analysis can focus on the algorithm.

Now, there is something to be said for languages which produce code that is nearly as efficient as the most efficient code you can produce with C, especially if it's easier to write it. But that's not the author's point.
The benchmark results are from several implementations of a longest common subsequence algorithm, the nested loops shown earlier are probably not part of that algorithm and were only meant to illustrate aliasing issues.
London Review of Books: The Satoshi Affair
Could you please elaborate on what needs improving in the docs?

Btw, the whole kotlinlang.org is OSS, and you can correct things you don't
Ehhhhh.... I can't help but think that it's never completely necessary to use totally unrestricted pointers in 'C'. Might be convenient, but very nearly certainly not necessary. Even in systems calls and library functions, it's possible to never dereference a pointer in an unconstrained manner. But you have to be prepared to reason rigorously about those constraints.

Noting that the semantics of array access semi-equate to pointer dereference is well beside the point.

This fellow's "for" loop:
for (int i=0; i < 20000) {
for (int j=0; j < 20000) {
x[i][j] = y[i-2][j+1] * y[i+1][j-2];
}
}

shows that you don't even have to have unrestricted pointer access to have bounds violations - what's "y[i-2]" when i==0?

'C' is not for everybody. It's a systems programming language. As the space of activities related to computers grows, there's no good reason to continue to erect a strawman about the language and set fire to it.
FB is missing three significant differences. 1 - Consuming video is time consuming. There is no quick scan for key words etc. If you're locked in on video X there's no scrolling on, etc. Your experience, in a way, stops. 2 - Video is passive. Reading takes engagement. Those will effect the brain very differently. 3 - Video is not conversational. It's traditional top down broadcasting.

Sure FB might become more video but that doesn't mean it's going to result in the same attachment to the product, at least for adults.
Mods- put a (2006) in there please. The number-crunching ecosystem has changed drastically in 10 years. He also didn't mention what compiler he's using. Intel's ICC had a huge advantage over gcc 2.95.3 (or whatever was used in '06) especially in numerical methods. (Though, I'm not sure when Intel's MKL became semi-freeware; at which point there was a significant performance jump if one opted to use the lib appropriately in tandem with gcc.)

This guy also could have at least linked to a repo of his code... though none of that fancy github stuff was around, Sourceforge and CVSweb was around back then. Without the source we can't really accurately judge, well, much of anything. Compiler flags, JVM tunes (was it warm?), source code, data sets, or hell, even mention of compilers.

Edit: Though his point held hm, not quite 'true' categorically, but you could argue the point. Around '06, Fortran was still largely used, at least bioinformatics (sequencing, attempts at heuristic folding .. stuff), weather prediction, and was a perfect fit for linear algebra.[1] It was accessible and fast enough to be used by post-docs who didn't write software for a living, so presumably the ecosystem was founded then continued to develop within Fortran. Even if it was possible to outperform your simulations in C++ (I'm sure you could get at least fairly close), all of the work you were building off of (e.g. with your colleagues, advisors, etc) were Fortran-based.

[1] This is all hearsay from my father's / his doctoral students work from the late '90s/early '00s when I was in high-school, so I can't really offer sources on hand, but if someone really wants me to, I can fire off an email to him to gather specifics.
> Fahrenheit is a smaller unit of measure, and, as a result, more precise

This one always comes up and it's the worst argument to me. Just going from the shade, or out from cover of wind and you'll get more than a degrees temperature difference. What use is that extra precision in daily use? And in any field that actually needs the extra precision (science, engineering), you're not going to shy away from using decimals.
Hmm, isn't this an infinite loop? i and j are not incremented. I'm surprised that the program can end in finite time.
What living in space  does to your body
Is Functional Programming really slow?
They are still very much required for games/real-time rendering :-)

I hadn't heard ptex before, it's interesting stuff. Sounds like the reason it isn't in general usage for realtime stuff is the memory overhead: http://sebastiansylvan.com/post/casting-a-critical-eye-on-gp...
Cheating software like in cars but in Telecom companies
I was in Germany and use mobile Vodafone prepay (CallYa guthaben): it's the thing when you pay online or buy somewhere 15 or 25 EUR to upload credit on phone. I uploaded new 15 EUR, so I had 18 EUR overall. If you travel outside of Germany to i.e. Italy, Slovenia, Croatia, you get sms notification that new roaming is in use since 30.5.2016, costing much less than it was, like not 22 cents but 14 cents per minute. Anyhow, just by trying to call a German number I get smashed -> "not enough credit". I checked *100# and true, 0.20 EUR. I have no reasonable explanation how I lost 17.80 EUR in 1 second from my credit. Except unless maybe the other operator not on German side but in the EU land charged roaming. But still, its quite some fee then which cannot even be. Perhaps some cheating software like in cars is operational in roaming settings :) Did anyone experience similar? It occurred to me actually twice, once in past, also in roaming situation.
Why would middle management need unionization?