skysight-inc/HackerNews huggingface dataset:
Definitely a great musician and I don’t think most people in the US realize how influential Sakamoto and YMO were worldwide, and how famous they are in Japan. I did not know until recently.

Sakomoto, Haruimi Hosono and Yukihiro Takahashi created not only several seminal YMO albums, but also dozens of solo albums and projects with a sound that often preceded American and European music by a few years. They are credited with laying the groundwork for techno, electro pop, and dance music. Also, Sakomoto’s influence can be heard in 8 and 16 but Japanese video game music from the 80s and 90s. I’m fact, Yuji Naka is Sega even said he started programming after being inspired by YMO’s electronic music. Ryuichi Sakomoto offering to make a playlist for your restaurant is about like having George Harrison or David Bowie offer to do it.
New Market Network for Learning
Well... It's not to be expected the old processors would remain available after the introduction of their improved successors.
> So you never trample over the 0.1%. Instead you fix your code, or you fix their code for them -- which was probably due to your own bugs or undefined behavior in the first place. Or else you don't push.

Given the size of a monrepo, is it possible to run the entire test suite in one's development environment, or do they have another endpoint to push to to run tests on a dedicated server?
There are 300M guns in the USA spread across 3.8M m^2.

1M soldiers (O(current armed forces)), armed with all the equipment they have (unless they decide to nuke the whole country) could not take down a rebel force spread across most of the US (concentrated away from the coasts, of course ;-).

It's not just theoretical.
The headline's provocative but it may be worth observing that even the original duck boats were/are WWII surplus vehicles that I'm pretty sure don't meet modern safety standards and are possibly even worse after some of the modifications like canopies.

And presumably someone in government (in a lot of places) signed off on transporting people in these.

Yes, someone with more experience and even professionally licensed should probably have signed off on the mods. But no one OKing this service required it and it's not clear the modifications were responsible for what happened or it was just something that can happen when duck boats generally are operated in the way that they're operated.
What Makes Threesome Dating More Popular?
How does this work for booting up a database or other systems to run integration tests and such? I don't see anything about that sort of thing. Is the idea to bake everything into a single docker image and run that? Also, what are the resource limits (really, just interested in ram) for that listed price?
People also seem to forget that "Monorepo" or (many) "Microrepos" is not a binary choice.

You can have both tiny repositories which do a single thing and large repositories that consist of many projects. It's totally cool to have both, assuming your team can be trusted to make the appropriate choices as they create new projects.

> And then people forget how to make distributed repos work and claim things like "omg I have to make 1 PR per repo when making breaking changes!", as if it was a big deal or it wasn't a solved problem.

Is this a solved problem? I typically do make one PR per repo to resolve breaking changes, though it's certainly not a big deal. Still, if there's an easier way, I'd love to hear about it!
As a data point, we put the dependency graphs in a database at build time. When we have an emergency and need to push a library update to thousands of repos, we make the change, then trigger builds for all the dependents. We don't auto deploy (too risky), but we use the data we have to start nagging the owner of all the repositories to tell them they have to deploy asap. Since all projects are very small, they build and deploy very, very quickly (a few minutes at most for the big ones).
That is a library issue.

Trying to make C 'foolproof' however, is an excercise in futility, and in any case, can only come about by morphing it into a fundamentally different language.

An argument in this thread, is that you shouldn't be able to pass an array without the argument being passed having some implicit 'size' element associated with it. That is NOT C.

Conflating pointers with arrays, that is C.

Again I feel the need to quote this:

"C retains the basic philosophy that programmers know what they are doing; it only requires that they state their intentions explicitly."

If you don't know what you're doing, don't use C.

C should be considered a 'specialist' language - much like doing brain surgery - if you're doing it, you better know what you're doing, else go be a GP or something.

And, if you're project doesn't absolutely require that you use C, don't use it. Instead, use something that is more 'foolproof'. (and I don't mean C++!!!)

D should focus less on being a better C, and more on being a replacement for C++. Then, I might take D more seriously.

No attempt to morph C (i.e. the language, not the library) into something else will ever succeed.

Leave C alone!
Distributed vs. centralized VCS has very little directly to do with many vs. monolithic repos. After all, git was originally developed for a project with a large monolithic repo. Distributed VCS and many small repos got popular around the same time, but that's partly coincidental (microservice architectures getting popular, npm community preferring extremely small libraries) and partly because of GitHub making it very cheap in money/time to have many git repos.
>In reality, most small restaurants and cafes just use Spotify.

I've even been to cafes where every few songs were interrupted by an ad about the benefits of upgrading to Spotify Premium....
(Regular) Folks' Models of Home Computer Security – Rick Wash [pdf]
What newer HPC product is replacing this? It seems like the Phi might be dead end, at least for the foreseeable future.
Of course an average civilian wont be able to match the training and resources of a soldier. The idea is to raise the cost of engaging the civilian populace. No government wants to rule over piles of ruble and streets full of corpses.

Occupation is already expensive and essentially temporary. Look at the situation in Afghanistan, the US invades and occupies the country. As they begin to withdraw, territory is taken back by the Taliban and warlords, they simply bide their time and wait for an opportunity to return.

An armed populace changes the math around occupation and engaging in violence. Of course this also leads to other oppressive mechanisms like propaganda and manufacturing concent, but at least people aren't dying. Its a step in the right direction.
Microsoft's Next-Gen Xbox Will Focus on 'XCloud' Game Streaming
So is there not, like, some kind of government agency that certifies whether a given boat design is safe to put passengers on? I know it says

> He said the boat was last inspected on Nov. 29, 2017, and was found “fit for route and service.”

But I assume that's more like when I get my car inspected. This is one of those things I assume exist in society, but I guess I really have no idea.
There is a set of code changes locally and those changes are bundled off to the test server to run the full test suite? That's a branch.

Now let's say I break a project sharing this code and because I'm not an expert in all 2 billion LoC and 3000 projects google is running I need to enlist some help in fixing what I broke. Presumably there is a way for the developers on that downstream project to pull in my change set? That's a shared branch.

Now assuming I can get all of these planets aligned correctly I'm going to need to take this set of changes and put it into the master version aren't I? That's merging my branch into trunk.
The Vital Question: Energy, Evolution, and the Origins of Complex Life by Nick Lane makes the case of the evolution of life from the vantage point of energy transfer.

I found the book accessible and compelling.
You're arguing for the nonexistence of something that obviously exists. There are tens of thousands of engineers at Google working in this manner on one of the largest codebases ever assembled.
> Yes, someone with more experience and even professionally licensed should probably have signed off on the mods. But no one OKing this service required it and it's not clear the modifications were responsible for what happened or it was just something that can happen when duck boats generally are operated in the way that they're operated.

From the article:

"In the water, duck boats are like a “sinking coffin” when they start to flood, said McCaskill, who plans to draft legislation proposing stronger safety standards for duck boats."

Forgive the dead horse beating, but this is why it's frequently said on HN (and in general) that safety laws and regulations are written in blood. People die, gaps are identified, gaps are closed, time passes, people complain about regulation.
> Chavez and Maduro are not leftist.

Are you serious? Do you know anything about the beloved "Bolivarian Revolution" and its policies?
Convert between XML and native Python data structures with jxmlease(2016)
> I mean, this is the argument for having good integration tests.

Maybe companies like Google have very, very strong code hygiene, but at most places I've worked, sooner or later there's a project that had a tight deadline and someone thought it smart to cut corners on the tests. Or the test s are there but they're bad. Or incomplete. Or worse, some system was just too hard to test and not updated frequently enough, so it requires manual testing.

Having "eventual consistency" for this is quite nice. Push a breaking change, update what you can, run tests, speak with owners, get deployed what you can. Keep tab of what you couldn't. Then do what you have to do to get the stuff tested (even if it means manual) and gradually become consistent as these things get pushed to prod...and hopefully next time its easier.
> Someone makes a commit to library code and production magically breaks? How does that happen?

With insufficient tests and broken release processes.
The speed you get is far more dependent on the signal strength, not the speed of the modem. That only comes into play when you have a perfect signal, so realistically (as a perfect signal is rare), modem speed plays almost no part in speed limitations.
> So of course, with this uninfringed right, you have people killing their spouse, children accidentally killing their family members, people seeking help after a car crash getting shot [1], increased rates of suicide, etc. etc. That's not to mention otherwise lawful firearms owners shooting up schools, churches, and theaters.

You're leaving out some key factors.

First, firearm violence in the US (like violence in general) is highly locality dependent. It's not a coincidence that the incident you linked to of a woman getting shot while seeking help after a car accident happened in Detroit. Most of the US has
a rate of violence (firearm and otherwise) than is at or below the norm in European countries like Switzerland. The statistics you see don't show this because they average over the entire country instead of separating out the particular areas where almost all of the violence actually happens.

Second, the localities in the US that have high rates of violence, including firearm violence, are all inner cities that have been run for decades by liberal governments that have imposed strict controls on firearm ownership. The rest of the US, which, as above, looks like Switzerland as far as violence is concerned, has much more reasonable policies on firearm ownership. So at least in the US, the data does not support the common claim that gun control reduces firearm violence; it supports the opposite claim.

Third, the mass shootings that make the news are most often not perpetrated using firearms that were legally owned by the shooters. Either they were legally owned by someone else and the shooter got access to them (illegally), or they were illegally obtained by the shooter in the first place.
It's the Knights Mill family - https://ark.intel.com/products/series/132784/Intel-Xeon-Phi-...
This seems to refer to what Pages uses for fonts and not the system font panel.

While the standard font panel does seem over-engineered, I think it has the things discussed: font grouping, full keyboard access (if you focus it), etc.
Now I really want to see the TeX based solution :)
Kakistocracy seems to sum them up

https://en.m.wikipedia.org/wiki/Kakistocracy
there are literally 60+ startup distributions that try to sell a "distribution as a service" for the upstream code that is free.

I think most if not all of them will fail, and as usual, the big 3 or 4 will win the market (if I had to bet: Google, Red hat, Canonical and maybe the guys at Heptio that are really cool and got the right attitude)
The tweet that it refers to: https://twitter.com/cpeterso/status/1021626510296285185
I wish I knew how to do that
You're right, but I suspect that one couldn't find a modern naval engineer who would approve any design based on a boat with insufficient flotation. If you cut a modern factory-built boat in half, both halves will float. If one of these duck coffins springs a leak, it's going to the bottom. So, the focus on the engineering degree isn't totally off-base, because a qualified engineer would just "nope" the whole thing.

The NTSB really should have put an end to this industry in 1999. It's tough to imagine that they won't fix their mistake this time around.
> I think you and the other commenter are seriously missing the point.

It sounds more like they are disagreeing with the point, which is not at all the same as missing it.
Ask HN: Is Spectre just as likely with RISC-V?
I am very unrelated to CPU design. There are a lot of us hoping RISC-V will be in our future computers.

As I understand it, processors from AMD and Intel are quite liberal with the x86 instruction set. They [can] act like complex virtual machines which re-order and tentatively execute later instructions against known data in the hopes this will be used (if the right branch is taken). This can offer better performance, but the issue is information being leaked unintentionally when that path isn't taken.

1) Would we be in the same boat with RISC-V?

2) Are RISC-V processors even "there yet"? Are there RISC-V processors currently doing speculative execution?

3) Is there anything in the RISC-V spec that makes something like Spectre less likely to happen? Does the RISC-V instruction set lend itself in some way to make Spectre less possible? A [believed] benefit of RISC-V is that with a reduced instruction set, things become easier to reason about.

4) Is speculative execution even a goal for RISC-V? Can a reduced instruction set offer optimization opportunities that make speculative execution not worth the risk? Can RISC-V be competitive without it? (much speculation here)

Again, I am very uninformed. I think we'd be in the same situation but I thought I'd ask.

(Thank you for entertaining my hypothetical?)
In this case, the near hurricane force winds are likely the largest contributing factor to the capsizing of the boat. A perfectly engineered boat, if not engineered for hurricane force winds, would also likely capsize. Weather can be hard to predict, but there were warnings issued and someone obviously 1) wasn't aware of the warning 2) ignored the warning or 3) thought the boat would be back in time before the winds kicked up. Breaking t-cells can make a calm day turn really quickly.
> Shouldn't we update that to include one-time passcodes like we do know for most things?

Some people I know are still not comfortable using an ATM, if you add passcodes they are going to have a very bad time.
The irony here is that you're asking how to use an essay about avoiding self-absorption in order to accomplish your goals more efficiently. It's not about your goal when you're in a grocery store, it's about the fact that you can't focus on anything other than your goal.

The idea is not that there's a profound insight hidden in there. In fact, the essay repeats several times that there's no trite lesson or platitude to walk away with, and that the basic idea is already obvious - the world doesn't revolve around any given person. What's not obvious is exerting the mental effort to consider that fact when you feel like you're the only person who has any self-awareness in a crowded grocery store.

On a more practical level, if you're looking for a lesson then this is close to it - you get in your own way, intellectually speaking, by defaulting to the easy path of discounting the myriad reasons for other peoples' behavior while rationalizing your own. We tend not to think about the things that are so obvious they're dreadfully mundane, but because of that we close ourselves off to insights that could be very helpful but for the fact that we're locked into our first-person perspective.

More succinctly: if you find yourself thinking that you're surrounded by people who lack self-awareness, you might be lacking some of it yourself.
It was also the name of a 3D desktop environment from Sun showed off in 2003. https://en.wikipedia.org/wiki/Project_Looking_Glass
Would anyone accustomed to boating get in one of those things? They don’t create a first impression of seaworthiness.
Can’t you create a branch and merge the two branches you are interested in into that?
Honey: A Game Engine and Game Engine Tutorial – First Post
Ayo! I'm making a game engine and writing a tutorial about it!

Whyyy?

Unity makes painfully clunky games, good languages like Python and Javascript are only good for making smallish games, and C++ is still super unpleasant to work with.

C++ is my least favorite programming language, but it's also still the best way to make professional games, the kind you can put on the Switch and in the Steam store. I'm not good at C++ and neither are most of the people I know, especially in the game making community.

I figure we could learn together and make something really nice. So I give you Honey, a free open source C++ game engine with a focus on simplicity, cuteness, and smoothness. Honey is a work in progress and always will be. Every piece of code ever committed to Honey will come with a teaching blog post.

I'm about 12 commits into making Honey, so it's still preliminary, though I can use it to make simple stuff like http://friendsonmountains.com/ABearCs/. But I'm making decently speedy progress, so some time later this year, it should be something people might want to use.

Join me, and let's learn to make a horrible thing into a nice one!
edit: never mind, deleted the comparison to the misuse of “engineer” (can’t delete post anymore).
Smaller repos force different components to expose APIs, but I don't think it forces or even encourages the APIs to be well designed. In some cases, having work spread across multiple repos can impede iterative development, meaning that you risk half-assed or, uh, two-and-a-half-assed implementations.

Also, when someone's asking for review for a change that encompasses, say, a change to a service, a change to a client library for that service, and a change to 2-3 other services that use that client library, I know that I cringe a little when suggesting a change, knowing that to implement it is going to require a commit on all of these different repos, waiting for CI to run on each one, etc. I try to only use that impulse to counter the urge to bikeshed, but the temptation is there.
> Is this a solved problem

I don't mean that it's magical, just that it's not particularly sorcery. Instead of making a breaking change, add new method, deprecate old method. Update projects, then get rid of old deprecated method. Because they're distinct you can do this one by one so some project can reap the benefits without having to wait until all the problems are solved.

Some people in this thread act like its freagin impossible. Avoiding breaking changes in APIs or proper deprecation strategies is an art everyone developing software should know: sooner or later they'll have to contribute to an open source project or have to make a more complicated breaking change or SOMETHING and will have to deal with it. Even if they use a monorepo. And when it happens you don't want it to be the first time anyone deals with it.
Sorry for the opaque comment. Was gushing over the cool exploits of the "Inception Group" or "RedOctober APT" - believed but not proven to be Russian espionage.

https://www.symantec.com/blogs/threat-intelligence/inception...

https://securelist.com/red-october-diplomatic-cyber-attacks-...

James Bond level epic awesomeness and sophistication. Keep reading if you want to nerd out.
Windows now tells me my computer is at risk because I refuse to give all my data to OneDrive. Their rationale is I'm at risk for cryptolockers, but the ulterior motive is clear.

I had to change a registry key to stop it from installing Facebook and Candy Crush on its own.
STILT (YC W16) Is Hiring Senior Engineer – Full Stack Development in India
Stilt (YC W16) is building an online bank for those typically underserved by the existing credit bureau reporting process, customers who are new to the United States banking system, and those with “thin” or no files. We are a Y-Combinator backed company based in San Francisco, founded by an immigrant team with expertise in finance, technology, and machine learning. We are working hard to make financial services simple for underserved applicants by building an institution that uses cross-country data, better credit risk scoring, and operational efficiency. Stilt has now served immigrants from 100+ countries.

As a Senior Engineer, you will:
- Work on a wide range of problems related to systems, processes, and technologies and own it end-to-end
- Ship features that will enhance Stilt's consumer-facing products
- Collaborate with senior management, experts in various fields and implement business logic in software
- Develop robust and consistent codebases across the organization
- Convert ideas to prototypes by quickly assembling together different technologies and frameworks
- Be part of an early-stage startup and be privy to critical decision-making processes
- Integrate third-party APIs for providing payments, document signing, and fraud detection
- Develop essential processes for development, testing, and deployment

You will impact:
- Stilt’s core lending platform that improves key business metrics for the business
- Internal tools that will be used for compliance, legal and loan operations
- Credit modeling platform by working closely with the data science team and provide your technical expertise in developing a scalable system

You should have:
- An undergraduate or graduate degree in Computer Science or a relevant field
- 4+ years of experience in a fast-paced environment.
- Experience with various technologies, and take pride in being a generalist
- Familiarity with server hosting, cloud-based systems and systems operations
- Knowledge of Python, Angular, React, Java, Github, REST APIs, HTML, Javascript, testing processes, AWS, Azure, HTTPS, SSL as a plus point

Email us at: jobs@stilt.co
Yeah thats right. I build race engines as a hobby (currently have a cp-carrillo mazda BP in the works) and (I like to think) I have an understanding of mechanical sympathy. Obviously performance engines have different tolerances to mass-produced consumer items, but I like to treat them the same.

The benefits to slow driving is that it also brings the drivetrain up to operating temps as well - it's no good if the engine's at a good oil temperature but the differential and gearbox is still icy. But even letting the car idle for 10-20 seconds so it can push oil around the block, fill the galleries and start filling the lifters/head will help extend the lifespan of an engine, and then combined with a slow initial drive to allow everything to come up to temperature you should be able to give the car a bit more life.
SiOnyx Aurora Night-Vision Camera