skysight-inc/HackerNews huggingface dataset:
I'm a bit sceptical about the explanation for base10, especially in Europe.
The UK changed from a base 12 money system in my lifetime, and the history of the metric system doesn't go back all that far: https://en.wikipedia.org/wiki/History_of_the_metric_system
More info here:
https://en.wikipedia.org/wiki/Duodecimal#Origin
20 copies seems ridiculously redundant evolutionarily speaking. There must be other uses for this gene that having any fewer would mean a lower survival rate.

I wonder if this means resistance against mutation and lower rates of adaptability to environment?
I've been going back and forth on this for a while as I work on a product that allows users to build applications in a drag and drop visual manner.

What I've seen is that while novices fairly quickly ramp up and get productive generating basic CRUD apps rapidly, they also rapidly hit a wall in two ways:

1. It can be hard or cumbersome to express more complex logic
2. The drag and drop interface often leads people to -assume- what the runtime will do.

Right now, I'm leaning toward feeling that visualization should be a tool to understand the _behavior_ of what one has written, but not necessarily the thing one manipulates to express a program. Ballerina seems to be this, so I'm excited there!
Output, and fuels.

Thermoisotopic generators generally rely on plutonium, which is in very low supply, and generate only about 100-200We output AFAIU.

That's enough for electronics and comms on a deep-space mission, but doesn't offer a whole lot of surplus power for planetary activity. Among the reasons that lander craft are so slow-moving (they basically manage a slow crawl) is power demands, though other factors, including navigation and stress, are considerations.

https://en.m.wikipedia.org/wiki/Radioisotope_thermoelectric_...
Relying on a third party isn't nearly as bad when the third party is also you!
> Although it is nice to have more funds available, which increases the competition among VCs, the main point is not lack of funds.

I agree on that, on the other hand I don't see the lack of market as a big problem. I like to take Spotify as example, it started in Sweden, which is a market comparable to the Swiss one in terms of size, but after the first prototypes and early versions, it went global almost immediately.

Schneider-Ammann said that a change of mentality is required in Switzerland. He noted that while in the US, business failure is greeted with a “better luck next time” or with a similar attitude, on the other hand, in Switzerland, “if you fail with your business idea here everyone points the finger at you. You are branded a looser”. This seems to be the main goal and I totally agree with him.

IMHO, a company can move to a global scale from the start with the right plan, but it's the mentality and the fact that Swiss VCs care more about patents and product protection preventing Swiss Start-up to compete with the rest of the world, instead of caring about quality of the actual product and picking the right time to enter the market.

I heard some stories about companies collecting 500-800k in seed investment, spending 50% of it in legal fees protecting a product they still have to develop, failing later in execution for lack of cash... this is what, I think, needs to be fixed in Switzerland.
Oh no! You should take a break after 4 hours. Otherwise you lose focus in the afternoon and become less productive!
A set of best practices? It rather looks like a set of random thoughts.
How do you collaborate on a branch using this workflow? The constant rebasing means you can't have multiple devs pushing to the same branch.
Average ongoing rents are relatively ok, but bringing in new people often means paying top market prices, they can be double to quadruple an average ongoing rent.
Sterling-cycle generator, utilising heat pipes, based on this study (PDF):

http://permalink.lanl.gov/object/tr?what=info:lanl-repo/lare...

Tracked via Wikipedia, which has a brief article:

https://en.m.wikipedia.org/wiki/Kilopower
When the calendar becomes more important than the quality.
An issue that could have been solved by watermarked pictures.
I think it's the compilers that have perverted the language to such an extent that it's become ridiculously difficult to understand, and so it's the compilers that must change back to being less obtuse and adversarial.

The C standard even suggests, when defining undefined behaviour, that one of the possible options is "behaving during translation or program execution in a documented manner characteristic of the environment". If signed int arithmetic on the hardware wraps around upon overflow, then take that into account when optimising and don't assume it can't overflow. This is how C programmers want the language to work; compiler writers and standards be damned.

I've written plenty of Asm and also looked at as much if not more compiler output; and while the latter sometimes pleasingly surprises me, it's usually pretty evident that it was not generated by an intelligent entity. (And countless times, I've obtained size and/or speed savings by replacing the latter with what I would otherwise write.) My general impression is that there aren't enough highly-skilled Asm programmers working on compiler development --- there are many reasons I can think of for that, but one of the things I've always wished to exist is a simple, straightforward C compiler with "understandable" output and optimisation that creates results closer to what a human Asm programmer might write; with the associated optimisation advantages and predictability. This means not assuming anything just because the standard says so, but taking a more holistic (for lack of a better word) approach to compilation and optimisation.

A long-time favourite post on this: http://blog.metaobject.com/2014/04/cc-osmartass.html
Like said already create a ticket instead of a to-do.

But also, instead if writing todos, explain the context and reasoning behind what needs to be done instead. In the future when this code is visited again this will help you or others to get into the right mode to make a proper decision about what to do with this code.
Maybe the reason to do something is no longer valid, if the intention is properly documented the decision can be made at that point. This allows for proper refactoring instead of skipping todos and keeping code for legacy reasons.

So instead of: //todo: remove this code

Do: // required for legacy API clients, should be removed after last client is deprecated.
It's not clear from the text how they define "Swiss startups". For example, being a foreigner, can I start a company there and ask for an investment?
> plutonium, which is in very low supply.

Thermoisotopic generators are a bad idea for general power generation for a colony for other reasons (they're low power, you need a lot of them), but it's not a problem that they're in low supply.

That's just because we haven't been making more plutonium recently, because we haven't needed it. We could simply make more.
Regarding the charging stations & related accessories, wait till Apple make its own electric car and I absolutely P_R_O_M_I_S_E you that action #1 on their agenda is to ensure that they use their own cables and fuses!!!!! (that will cost x20 the competition's accessories of course).

Joking apart, this is good news for Humanity and planet Earth!
> Place your test files next to the implementation.

ok.

> A resource always should be plural in the URL. Keeping verbs out of your resource URLs.

What does it have to do with Javascript projects?

> Avoid js alerts in production

alert is a DOM API, it doesn't have anything to do with Javascript.

-

Barely anybody pointed out the fact that this "guide" mixes up things that have nothing to do with each others.

How is file organisation related to how one name "subresources" in a rest API or browser alerts ? it isn't.

This isn't a serious document. It was hastly put together with no real considerations whatsoever and named "best practices" without any sources or links to give weight to these opinions.

Finally, as I said multiple times, coding style guides, "best practices" that cannot be validated automatically on a CI server are worthless and a waste of time in an business environment.
Facebook fights U.S. gag order over government search warrants
US Lifts Laptop Ban on Etihad, Emirates and Turkish Airlines
It's the other way around: EUR/CHF=1.09 means 1EUR=1.09CHF.

> [2011 to 2015] the Euro was exchanging [at] CHF1.20. [Then] the exchange rate stabilised to between CHF1.05 and CHF1.08 to the Euro, due in large part to further intervention from the SNB which discreetly set about buying up foreign currency to ensure the franc did [rise to] new heights

https://www.swissinfo.ch/eng/business/money--money--money_sw...
>which is _intended_ to be unconditionally true of safe Rust code,

I emphasized "intended" because it seems like we're talking past each other.

You: re-emphasizing Rust's specified design goal.

Me: emphasizing the current state of Rust compiler as reality which makes the statement "safe Rust has no undefined behavior" as not true.

(In other words, I emphasize the unintentional UB whereas you do not.)

>, because your conditional is equivalent to saying "if you write valid code".

If you look at the github issue, "1.04E+17 as u8" is valid safe Rust code which invokes UB.
But we're not talking about a nominal dollar change in prices. The point was that the real wages have gone down, and that's not a direct result of inflation because you would expect workers to demand raises in line with inflation if they had the power to. Instead, manufacturing workers don't have that power.
> 9.2 Operating on resources

Sure, let's pretend that GraphQL is not a thing. Yep.
Yes. The strength is the inverse of that.
> It's pretty wild to me to imagine that for all of our diversity and abundance today, there was much greater diversity of homonins at a time when we were much fewer in number.

Fewer in numbers means more isolation between groups.

In addition to that, early stages of culture may or may not have further augmented isolation. This is purely speculative of course, but we are in "imagine" territory anyways. Then the first group to develop cultural traits that somehow facilitated crossbreeding might have triggered a cascading melting pot effect, leading to the relatively uniform "modern human".
When I've been telling everyone that James Bond and other similar movies serve the same role as military parades in Soviet-block countries, and heavily scripted by the military, they told me that this is another conspiracy theory and I must be plainly wrong.

I wasn't.
A "Swiss Startup" is a startup actually based in Switzerland.
As far as I know, foreigners with permanent residence in Switzerland have the same rights of Swiss people, plus more than 25% of population is actual foreigner in Switzerland, so that should not a problem at all.
We are still talking $35k-$100k, in essence, the exact same price range that BMW lives in.
zfs send is also a general purpose file sync tool, it just has the limitation that server side and client side must use ZFS.

The advantage of RSync is that it is independent of the file system - which is at the same time a huge disadvantage of RSync, as it prevents RSync from performing optimizations which zfs send can do.
It's a bit of a wash, honestly.

You don't have to deal with Sendmail cf files, and there are secue options other than qmail.

Though yes, it's rather the PITA.
The concern was never about a nuclear reactor having a failure mode on Mars. It was about the rocket carrying the nuke having a failure mode and spewing radioactive fuel over central Florida.
If somebody asks you what "cat" does, do you say "It copies its input to its output, unless there's a bug in cat or the C compiler that compiled it or cosmic rays hit the program on disk"?
Fear of radiation is more dangerous than radiation itself
It is also linked at the IOP page itself.
Caveat Emptor. If you're running a business that depends on a third party hosting assets related to your product, reading and keeping up with the terms of service isn't BS, it's mandatory. If you don't want to do your due diligence, then host everything yourself and eat the bandwidth costs.
> If signed int arithmetic on the hardware wraps around upon overflow, then take that into account when optimising and don't assume it can't overflow. This is how C programmers want the language to work;

Don't speak for all of us.

Some of us may take the language for what it is, instead of assuming it to be a "high level portable assembler" which it is not, but which a particular implementation of it may be, thanks to the standard leaving much up to the implementation.

It is this same leeway that (thankfully) allows smart optimizing compilers that can generate performant code for programs that are not omgwtf-optimized at the source level.

And it is this same leeway that allows very simplistic, naive implementations that do not go out of their way to perform crazy analysis to try and warn you about some corner case of undesirable behavior your code might hit.

You're right that it is the compilers can and need to change to accommodate different types of users. But I don't think every compiler should just go back to being a 1991 compiler; not every compiler needs to accommodate every user.
you want to slice your abstractions by domain logic boundaries

essentially by "what it does, not by how it does it"

eg let's say you want to do notifications for your site.

you want to have everything related to notifications within one folder and have the outside connect to it via one api (eg component)

in backends this would enable you to easily scale in performance (eg move to microservice or separately hosted instance) or team size (isolation in code, less awareness of the overall codebase "needed")

imo the next big web framework after rails will have this setup as a default

`app/services` instead of
`app/controllers, app/models, app/decorators, app/workers, app/assets, app/views, etc`
You don't have to run anything yourself, just "hold the key to the domain" so to speak. Relying on a mail provider to host the email server is fine, and if they try to take it from you, you can be up and running with a different provider in less than 10 minutes, with it fully probagated 24 hours time. You are still in complete control over the future of all email on that domain.
WannaCry Attack: Let’s Talk Cloud and Encryption
The ironic thing about this is that the link they post as a justification for rebasing feature branches onto develop is actually a very explicit reason _not_ to be rebasing in this situation.

The section reads like the author thinks that the problem with rebasing public branches is merge conflicts (it isn't; it's rewritten/diverging histories) and that interactively rebasing somehow resolves this problem (it doesn't).

This smacks of something that I come across all the time: strong opinions on how to use Git held by people who don't actually understand Git.
> uninhabited planet

By humans. By other life-forms is yet to be proven one way or another. There is already discussion of treaties to prevent contamination of any Mars biosphere by human missions there.

Also: what about the future? There's no point in sending a nuclear reactor to Mars if a future colonisation mission can't go ahead because the reactor has melted down...

Solar irradiance is approximately 50% less than on Earth. PV with high efficiency modules (the same ones they use on satellites) is also viable. I wonder if anyone has run the numbers on the cost of shipping a reactor Vs. the cost of shipping a football field of PV modules there.
Yeah meta-moderation, limited mod points and a secret algorithm for earning mod points based on reputation works pretty well. Oh.. and a maximum score for comments.
Curious why they felt the need to do this at all in this way. Their goal is to maximise profits.

How does making people super angry about your service serve that purpose? And they had to know. They had to know the numbers of conversions after the ToS change and whether or not their was an uptick of people seeing this and converting. They had to know that they were going to affect a lot of people overnight. This was not accidental in any way.

So what's the difference in money you'd make/lose by putting it up front and center all over your site saying "Photobucket is transitioning away from the free tier". A blog post? An email? A release to the press?

At "worst" they'd find themselves in a situation where most people stop using their service. I put it in quotes because, this also means that the incredible cost of hosting people who never intended to pay also goes away. It's tough but hey, it's still a win for Photo bucket.

At best, if done right, they might even earn the goodwill of people and convert more people over than they'd expected in the first place.

Doing it this way can never get them anywhere more than "worst", and in the long run it'll probably be actually worse as people who might have considered paying will be spooked/pissed off and will vanish into the ether.

I can't understand how anyone thought this was a good execution plan to maximise business profitability.
Because thousands of times in my life I've had more time the day after today.
Other than for a proverbial handful of people in the world, it isn't
Indeed. I just never really internalized all the operator precedence in C/C++ so I never write code like `a + b >> c`; I always add parenthesis when mixing arithmetic and bit operations.
And if you want to pretend that you are hacking open this: https://haxor.secapps.com/
"Use stage-1 and higher JavaScript (modern) syntax for new projects. For old project stay consistent with existing syntax unless you intend to modernise the project."

That seems doesn't seem like a good idea. I can understand recommending Stage-2 and/or Stage-3, but stage-1 seems premature. Stage-1 in the TC39 process is still proposal stage that is flagged for expecting "Major" changes in the spec and possibly the syntax of the feature. Being stage-1 also is a poor guarantee that it will progress to future stages or become part of the spec. Stage-2 at least signals that the committee think its likely to eventually become part of the spec with only minor revisions.
Intro to Middleman
Seems like a perfect situation for Photo Voltaics...
I think that's a great example of how optimisers have gone off the deep end: no reasonable human programmer would think "I can't figure out if this loop terminates, so let's just leave it out", but that appears to be the default behaviour in this case --- when what should happen when the optimiser "gives up" is that it should just translate the code verbatim.
Volvo to drop traditional engines
Or require those parties to comply with sensible and uniform user-centric standards of behaviours.

You're relying on a directory service ... somewhere, somehow. Your postal-service address is only as solid as the property and/or tenancy registry that's associated with that address.

(There may be some way of coming up with a p2p system based on UUIDs and PKI plus a web-of-trust reputational vouching, but that is not an alternative I can switch to tomorrow for general use.)
> Galois theory without functor...

The category-theoretic accretion to Galois theory is a much later addition; Galois certainly didn't think in those terms, and I think that it is not obligatory for an expository (or even a mathematical!) treatment of the subject to do so.
I usually choose not to turn on red when driving in the US when when it's busy. I consider it safer to wait for explicit priority.
If it's so - how does that work on worldwide scale, on the legal side of things?
I don't think anybody cares about the long term service of Photobucket. Everybody knew that was going to happen.

It has happened to all image uploaders in history, and it will keep happening forever, since image uploaders are 1) a money-losing business (people will flee as soon as you stop hotlinking) and 2) have no real value (how much time does it take you to write an image uploader? probably one of the first things you do when you're learning to code for the web)
> the claim that safe Rust doesn't have UB (that isn't considered a bug in the compiler) still stands

Yes!

> If you mix in unsafe code, bad things may happen

Yes!

My point was only that those bad things may also happen after the unsafe block that is their root cause. This is in reply to parent's "all of these [UBs] are inside of unsafe blocks". They aren't. They are caused by something inside unsafe blocks, but they may also materialize after.
Which federal laws do you mean? Contract law is a state thing.
Just today i exchanged bitcoin for litecoin on a website called shapeshift.io that anonymously matches up buyers and sellers, through a vpn, and the service doesn't even require a login. I can just as easily exchange back with a different seller at some point in the future. Explain to me exactly how you think you're going to curtail that?
Robotics market forecast 2017-2022 just published
Given how GObject is implemented (void pointers everywhere ), that's not surprising.
Mini reactors are useless on Mars. The power they generate is waaay to low compared to the money that is needed to bring them there. Also putting nuclear reactors on sattelites almost never happens and is VERY DANGEROUS. It's what the Soviet Union did in the 70s-90s. The last sattelite launched with a nuclear reactor was in 1988.

You have to be pretty insane to launch large amounts of nuclear material from earth in a rocket that can randomly explode in our atmosphere.
It is a shame you have to adopt one of the larger frameworks like Angular, React, or Ember to get some tooling like this.

And certainly "gofmt" is sorely missed in every other language I've used since!
They don't have to build it on Mars. A kilowatt scale nuclear reactor is small and also safer and more portable. The Russians have already sent nuclear powered satellites into space.
If you're trying to teach someone OOP with their first language, I think you're doing it wrong. If someone is new to programming, it's far more important that people get an understanding of simple procedural logic first. Anything that gets in the way of that is just likely to put people off.

I don't think Python is a great language longer term, but its simple syntax and lack of ceremony makes it pretty much ideal for beginners.
I am a little bit more optimistic about it..I mean GitHub has recently introduced the GraphQL API..I guess that other SaaS's will follow - twitter, reddit, HN(or probably not) and so on.
ThoughtWorks is a pretty open place in terms of political discussions. This round is mainly to check the culture fit.
Revealed: Microsoft's Xbox One X Benchmarks
Glucose is used as fuel, whereas fructose doesn't have a direct pathway to be used as fuel, it must first be stored as fat.

You then have to have an absence of glucose in your body before you may metabolize your body fat. This doesn't happen often for most people, hence, the obesity epidemic from overconsumption of sugar.

That's the short version. The long, detailed version is available from YouTube, search for Dr. Robert Lustig's videos.
Bluetooth 5 chip for cost-sensitive applications
Example of "Reddit style comments" would be low effort jokes. Some subreddits are addressing this by using a convention where you can mark submissions with a "[serious]" tag, forbidding such replies (if there are any, they will usually be removed by the subreddit's moderators).

On HN, quite a few of them seem to get heavily downvoted (sometimes enough to mark them as dead, meaning you won't see them unless you explicitly opt in to see them).
I don't thunk so. You can find counterexamples in startups from Israel that almost always target markets in other countries. At the end you would need to move but you can start almost anywhere.
Off-The-shelf Linux Computers Compared: OEMs ZaReason, System76, and Dell
Show HN: One-liner for an isotropic sphere mesh in Mathematica
Not sure it is very useful, but I found it cool:
DelaunayMesh[
Table[
Normalize[Table[RandomVariate[NormalDistribution[]],3]]
,1000]
]