skysight-inc/HackerNews huggingface dataset:
The Linux kernel uses a macro called RELOC_HIDE to stop gcc from seeing through the conversion from pointer to integer in these cases: https://elixir.bootlin.com/linux/v4.18/source/include/linux/...

Edit: a good explanation of that macro is at http://lists.linuxcoding.com/kernel/2006-q3/msg17979.html :

"The reason for it is that gcc assumes that if you add something on to the address of a symbol, the resulting address is still inside the bounds of the symbol, and do optimizations based on that. The RELOC_HIDE macro is designed to prevent gcc knowing that the resulting pointer is obtained by adding an offset to the address of a symbol. As far as gcc knows, the resulting pointer could point to anything."
Not an intro to QM. Just reviews some of the math used in it.
> Ironically, I think this Soviet-esque mentality that "people who disagree with idea X are dangerous" is dangerous!

Every, single social media platform, political show, talk show, no matter the side.
Apple Says No to Sex and Violence for Its Streaming Service
I think the "uncomfortable champagne glasses" would make a great party game :-)
In Denmark, there's a special tax bracket for expats, where you pay only about 33% of your salary (instead of the standard 50+%), I think you're eglibigle to use it for up to five years.
Then say that instead of asserting that it doesn’t exist. I agree, there is a discoverability problem with 3D Touch.
It's remarkable that the components of the nerve system are very ancient and were all in place in the ur-bilaterian.
Is it worth submitting pull requests to fix?
I agree with you wrt the battery, but I would prefer to put an aftermarket case on a more fragile phone than to buy a rugged phone that supposedly doesn't need a case.

Both are going to be badly scratched up if dropped on or dragged across a rough surface. A cheap aftermarket case, though, is much easier to replace than the backside of a phone. In other words, a replaceable case has many of the same benefits as a replaceable battery.
You did not get that failure mode. If you want to fail at file not found, wrap it in a RuntimeException or IllegalStateException or something. You don't even have to create a new class, just use one of these 2 built ito Java.

For example: you store a conversion factor in you config file (eurostodollars=1.12 or whatever).

If you have an empty catch block, you now have a null Reader object or something. Next read will throw an IOException, which you also swallow and you now have an uninitialized config value. Except that one will be zero instead of null.

500 km further in your code, a month after you started the app, that zero gets used in your code.

amounttopay+=eurostodollars*euroamount;

This will not fail immediately either. No, it will do something weird. In the best case, you crash for a really weird reason. More probably, you send out a file or web call or ... with insanely wrong data. Bonus points if you sign it with a private key, then you're legally bound by whatever nonsense you happened to promise. The next program in the chain might sit either in your company or not. It will swallow your garbage date wholly, do no checking of its own as this no-error-checking culture is pervasive. It will either crash and or do further damage. When the shit finally hits the fan, it will be a containerload of shit instead of a mouse dropping.

I saw this kind of scenario again and again. No , the app cant possibly start without database, that never happens, and anyway the next user will notice the empty database. Except after power failure in the middle of the night, when the database is still booting up while your app is reading the config from it. When business hour start, everything seems fine. Until it isnt.
EconTalk is good about not being like this.
It‘s just an observation. The apprenticeship system stems from the old guilds. There is no support yet for learning programming that way. It will take a while, the system evolves very slowly.
I think checked exceptions are a bad way of doing Result types (Result in Rust, Either in Haskell), and that those are generally better than unchecked exceptions. In my opinion, unchecked exceptions aren't that much different than checked exceptions. The difference is that you have to get them right at the level of documentation, not type signatures, and documentation usually doesn't have a compiler that will help you.

However, back in the Java 7 days, I think checked exceptions would've been made a lot better with a bit of syntactic sugar:

public void foo() rethrows* {
bar();
}

Where the meaning of the rethrows term is that the method throws whatever exceptions the methods it calls throws. The bottom level methods that throw exceptions would still have

This would make it easier to refactor code to change exception behavior. It would only be at the public API boundaries that you have to wrap exceptions to avoid changing the API or modify your method signatures.

Now that lambdas are here, checked exceptions are even more painful, so I don't think this solution would tip the balance. But for the language that we had, I think it would've helped a lot.

* rethrows might not be the best name. I'm more attached to the idea than the term.
They mean "an animal" in the cladographic sense as being part of the same evolutionary tree as modern animals, and not e.g. lichens or funguses. Specifically, they seem to have detected cholesterol (or some decay product thereof maybe) in the fossil, which is a lipid that only animals make.

The identity of the ediacaran fauna has long been controversial. They don't "look like" modern animals (all of whom descend from forms that appeared later, in the cambrian explosion), so they're hard to place. This is a big, big result if it holds up.

FWIW: this is the Wikipedia article you want to be reading: https://en.wikipedia.org/wiki/Ediacaran_biota
Many people believe that human rights are inherent to human beings and we are entitled to those rights in full as a result of our status as humans, not as a result of our birth in a certain place.

Whenever you see a country providing citizens human rights and denying them to non-citizens, that country is morally bankrupt.
I think it is important to produce students who are fluent in the fundamental concepts of software engineering and computer architecture. So being fluent in things like pointers, circular buffers, memory management, stack vs heap, etc. is really important.

I don’t think the specific language is that important. But completing the program being competent in (at least) one high level language and one low level language seems valuable to me. With a strong background in fundamentals, students to learn new languages pretty easily.

My personal favorites are python and c, but I don’t think those specific languages are too important.

I also think a strong understanding of practical dev tools is important. Things like:

- using version control

- user vcs in a team/distributed environment

- how to do code reviews

- unit tests

- etc.
Agreed. I see checked exceptions as kinda parallel to Rusts Result type (and its older cousins), which people seem to like.
I can't believe MSN is still around.
Serverless on AWS is the closest thing to an “eternal” stack. Utilize only managed, auto scaling, self updating services, and your app will keep running for a long time. Occasionally the Node.js major version in Lambda gets deprecated, but even so I think old deployments still keep running.
an empty try catch wont necessary make that happen. It could countinue with the assumption that it has a File when it doesnt, corrupting further things in its (uncontrolled) way out.
That's the gig economy perspective. What happens when you are deploying software on someone else's computers? There are often no "ops" and no "dashboards" but a single technically unskilled user trying to get some work done.

Don't get me wrong, I also think that Java's checked exceptions are not really useful but your argument is very one-sided.
Each is harder:

* return a result

* return a list of results

* return a list of results with a confidence weightins

* return a list of results with multiple weightings (confidence and complexity)

how many if statements would you need to write for each if this was applied to a 3x3 grid like tic-tac-toe? how would you know you are correct?
Poland has a flat tax rate of ~19% (if you run a business or are self-employed - a lot of developers are self-employed here) and it also has free health care and universities, up to PhD level... You don't have to pay 60% taxes to get these.
There was a book for kids published in the Soviet Union which describes some of these principles along with examples. I received it as a gift from my aunt and it was one of my favorite books. It was called something like "And Then Inventor Appears...". Anyone remember the book?
How close are those convolutional filters to the physical sight of animals? Were they designed specifically to mimic nature or they are artificial concept with similar purpose?
I think the authors has some good points, but I don't think the proposed solutions really solve the underlying problem.

In particular:

> But how do I know, that a method throws an unchecked exception? The compiler doesn’t tell me. Yes, you are responsible to document unchecked exceptions carefully.

Except if you try that, the same problem that makes checked exception problematic will bite you here too - except now it's easier to blame yourself than blaming the compiler.

If you write

void foo() throws FooException

all you can really say is "It might be useful to consider FooExceptions when calling this function".

- You can't guarantee to a caller that FooException is always important to consider - because, as the author correctly stated, there might be situations where you call foo() but it's formally impossible that a FooException is raised.

- You can't guarantee that FooException is the only important exception to consider either, because foo() might call other functions that might raise different exceptions on their own - a fact that you could probably read up in those other functions' documentations, if you knew you had to deal with those other functions in the first place.

This limitation stays whether FooException is checked or not.

In then end, what you'd like to know when calling a function is the complete set of exceptions this call site could produce at runtime. Checked exceptions were a an attempt to answer this question, even if it was a very clumsy and eventually unworkable one.

Maybe a better solution would be more sophisticated static analysis, which could try to answer this question as part of an IDE. However, this would require that the analysis tool get complete information about all abstract functions calls, interceptors and other things that could happen as part of a call. This seems somewhat doable with fully static languages like Go but seems to run completely against Java's philosophy of being extensible at runtime.
I did start earlier than the VIC-20 (with TRS-80 Model 2 at school) but you definitely take the title :)
Fond memories using this back in my computer architecture class. I think "spim -b" is forever ingrained in my mind.
> How is this argument related to the confusion of the terms Machine Learning and Neural Networks...?

We're talking about the title.

> The most appropriate term is the most precise one, in this case : neural networks

That is generalizing RNNs and CNNs into "neural networks". If I take a popular CNN architecture, chop off the final dense layer and activation and attach an SVM classifier, is it an SVM or a convnet I am using?

Somehow the title "The Elephant in the Room confronts faster_rcnn_inception_resnet_v2_atrous_coco,
faster_rcnn_nas_coco, ssd_mobilenet_v1_coco,
mask_rcnn_inception_resnet_v2_atrous_coco, mask_rcnn_resnet101_atrous_coco." (or the reverse) doesn't have the same ring to it and is probably inappropriate for the audience.
This?

https://www.amazon.co.uk/Suddenly-Inventor-Appeared-Inventiv...
I think the article is referring to a scene that would be unlikely, not make sense given the context. Like identify a grey mass in the middle of the street as en elephant.

"Confusing" would be a poor choice of word here though.
"public" meaning what. Both legally and socially, caring for children is mandatory.

We had a breakdown of extended family structure (aunts watching the kids for an hour or two) and neighborhoods (same but for elderly neighbors, sometimes compensated). Everyone knows child care is labor intensive. Nobody knows how to pay for it is all.
I think the problem is that checked exceptions seem to defeat the benefits of using exceptions.

You're better off returning something like Rust's Result type.
Why the PC Will Not Die – Bill Gates (1999)
For most western European countries, there are almost no case in which you end up 'on the street'.

Most countries have a system in which this is prevented in a tiered system (like the German example) where there is the utter bottom layer where you get just enough money to fulfil primary needs (health, roof, bed, food, power, water etc). This status often also means you get other things as well, like free education for people that really cannot afford anything. This basic needs for existence tier is no fun to live in as far as I've seen/heard, and is a pretty good motivator to get out of as soon as possible.

As far as I know, this is also why you don't see the same tent camps underneath overpasses you see in the US; unless you completely remove yourself from society (by choice or by mental status), there is no need for it.

Then, on top of that base layer, which is not something you usually get to, there are the layers that deal with cases where injury causes you to not be able to work, as well as simply losing a job (which is usually because your contract expired, the company no longer exists, or you did something yourself -- not the case where the employer simply said "we don't want you" -- they can't , not with a permanent contract). This layer gets you anywhere between 50% and 80% of your last salary in most countries.

Keep in mind, that with most of those constructions, a lot of systems are in place that prevent you from going that low, or staying that low, on the income/self-sufficiency ladder. This is because it was mostly modeled on the concept that enabling people to live is cheaper than having a bunch of people on the street, as well as simple compassion and empathy. A lot of it comes from historical concepts, but it seems to grow in the same direction.
5 things every software developer should know about software architecture
The Age of “Node.js And…”: Community and Ecosystem
Oceangate is offering tourists an underwater expedition to visit the titanic
I may be interpreting it wrong, but I don't think the requirement was "don't be humorous", I think it was don't do it just to be humorous. In other words, if the idea is humorous to some, that is fine, but you shouldn't try to create an idea just to fit a joke. Not sure if I've explained that clearly, but hopefully I've got my point across :-)
Same here (western Europe) but aside from a little complaining, nobody really wants it gone as it has too many benefits for everyone as whole. And as long as you 'know' the true cost of having an employee you can take that into account which makes it more of a math problem and less of a money problem.
Detecting planets with deep learning
Subscription decouples the reward for quality from the consumer.
A good system would create payment by time && Lines Read minus some Rewared for Content produced as Result by the User (Not emotional Engagment drivel in some comment, but actually contributing to a discussion).

Good Content would be peer reviewed by its readers, like it happens here on HN, and those reviews would in return garant those contributing some discount or even reward.

We are so far away from that like earth from mars.
TL;DW: Number of programmers doubling every 5 years means at least half of all programmers are completely inexperienced, overwhelming the number of teachers, so kids stuck learning by remaking mistakes.

OTOH, certainly worth the watch even if just from this point to the end, easy listen at 1.5x speed.
I’m not sure what you mean here. I just used safari 12 with extensions installed. Are there new restrictions for extensions?
>“The scale of the hit of RAZR is hard to comprehend. Charles Dunstone of Carphone Warehouse ordered a quarter of a million in pink. We thought he was mad, this was a third of the global projected sales. He wanted this crazy volume of the “boys” phone to sell to girls in the UK. We gave him exclusivity on the pink colour. When he sold 3 million we bought the non-UK rights back.”

Reading this makes me wince at the monoculture. I can imagine the meetings; "You mean women are a major part of the mobile phone market? And they spend money on high quality design? And some men like pink too? Oh, and you are saying some women don't? Here, let me write this down, this stuff is out there."
Conceptually, Pointer is a higher and a more well defined, level of abstraction than a raw integer.In much the same way as an Iterator is a higher and more well defined level of abstraction than a raw pointer.

The fact that an Iterator, a pointer and an integer all tend to be different ways of looking at same integer value is more or less an implementation detail.
Having programmed extensively in Java, C# and C++ I can say with confidence that checked exceptions is the most important thing missing in C++ and C#. Around the time C# was released there was a lot of debate around the topic of checked vs unchecked exceptions and this created an impression that Java's use of checked exceptions was "controversial". In fact it is a feature every modern language should have.

Exceptions that can be thrown by a method should be part of the contract of that method. Changing the list of the list of exceptions that can be thrown by a method is just like changing the parameters of the method. This is something that should cause calling code to fail to compile. This will allow you to inspect the calling code and decode how to deal with the new exception.

When the exception that can be thrown by a method is not known you don't know what exceptions to catch and what exceptions to pass through to callers. You can't rely on documentation because the documentation is not verified be the compiler and so is not reliable. All you can do is to run the program a few times, see what exceptions you get and handle them. Even if you are able to determine the full list of exceptions using this strategy, a future revision of the called method can throw a new exception and cause your program to crash. As a result, in large C# code bases it is common to see catching the base Exception class because this is the only way to prevent a crash. This causes exceptions to be "swallowed" because higher level code that is actually prepared to handle certain exceptions never get the exception.

With Java this problem doesn't exist. When you call a function you know exactly what exceptions can be thrown and you can catch (or pass through) exactly those exceptions. There is no need to catch the base exception class.
> and have to write an empty try-catch

I end up converting checked exceptions to runtime exceptions all the time:

try {
...
} catch (RuntimeException e) {
throw e;
} catch (Exception e) {
throw new RuntimeException(e.getMessage(), e);
}
You sure about that?

https://www.independent.co.uk/news/world/europe/marine-le-pe...

https://en.wikipedia.org/wiki/Laws_against_Holocaust_denial#... -- because apparently if we outlaw Nazi symbolism it will disappear.

France is even more awesome: Gayssot Act makes it illegal to question the existence of crimes against humanity as defined in the London Charter. Let that sink in - it is illegal to question.
I can totally relate. I sustained a wrist injury about 10 years ago from physical trauma which requires me to wear wrist braces constantly to this day so help manage the pain, weakness, and shaking. I’ve seen more doctors than I can count about it and I’ve yet to even receive a diagnosis. They just all assume I have carpal tunnel despite numerous tests which say otherwise just because I’m a programmer. When their carpal tunnel theory doesn’t pan out they just give up yet somehow every single one of them won’t admit they don’t know what’s wrong. I’ve researched as much medical material regarding my issue as I can and take notes to present to them since I’m not educated enough in the medical domain to go beyond potential causes so I present those notes along with diagrams of the pain locations and locked muscles as well as photographs of related skin conditions. And even then when I do research and present my findings to help guide them along the way I still have to fight them to even attempt further diagnostic techniques. It’s a frustrating issue and it’s something I’ve been wracking my brain with on how to help address it in anyway I can.
But that seems to be limited/worse/more when you get 'halfway' through France on the map, it's more abundant when you get in the mediterranean areas. Not sure why, but it's an observation; it's almost as if the concept of work replaced the actual merit of work.
the same difference between a raven and a writing desk
Show HN: Thi.ng/hdom – S-expression based, pure ES6 UI/VDOM components
https://github.com/thi-ng/umbrella/blob/master/packages/hdom...

Lightweight UI component tree definition syntax, DOM creation and differential updates using only vanilla JS data structures (arrays, iterators, closures, attribute objects or objects with life cycle functions, closures). By default targets the browser's native DOM, but supports other arbitrary target implementations in a branch-local manner, e.g. to define scene graphs for a canvas element as part of the normal UI tree.

Benefits:

- Use the full expressiveness of ES6 / TypeScript to define user interfaces

- No enforced opinion about state handling, very flexible

- Clean, functional component composition & reuse

- No source pre-processing, transpiling or string interpolation

- Less verbose than HTML / JSX, resulting in smaller file sizes

- Supports arbitrary elements (incl. SVG), attributes and events in uniform, S-expression based syntax

- Supports branch-local custom update behaviors & arbitrary (e.g. non-DOM) target data structures to which tree diffs are applied to

- Suitable for server-side rendering and then "hydrating" listeners and components with life cycle methods on the client side

- Can use JSON for static components (or component templates)

- Optional user context injection (an arbitrary object/value passed to all component functions embedded in the tree)

- Default implementation supports CSS conversion from JS objects for style attribs

- Auto-expansion of embedded values / types which implement the IToHiccup or IDeref interfaces (e.g. atoms, cursors, derived views, streams etc.)

- Only ~5.5KB gzipped
> a low confidence score

Neural nets should return a low confidence score. But, the popular approach (described below) ignores that. Neural nets ignore confidence because of a technique called softmax [1].

This happens as the final operation of a neural net, and is required for training.

Softmax is a tool to make an array of positive numbers look like a probability distribution:

out = x / x.sum()

x[i] is a class prediction, but x.sum() != 1. Say if the network was uncertain, x[cat, dog] = [0.03, 0.01]. These are small values that do not imply great confidence (the network was trained on vectors with out.sum() = 1. The network would predict “dog” using softmax because out[dog] = 0.75 > 0.25 = out[cat].

But then in inference/prediction, the confidence is ignored. What if x.sum() is small? That would imply that the network is uncertain.

[1]: https://en.m.wikipedia.org/wiki/Softmax_function
Design patterns are great, but the problem they try to solve is "how to build software well". but what about patterns for "how to use/design software to solve problems"?
Nothing about checked exceptions inherently prevents the failure scenarios you list, particularly the one about the power failure.