skysight-inc/HackerNews huggingface dataset:
Microsoft dictates what a general purpose PC manufactured by others has to do to be compatible with Windows; vendors that don't care about being able to run Windows can refuse to abide with anything Microsoft says. (Apple doesn't meet Microsoft's standards, for instance.) Linux is an operating system designed to run on computers that meet Microsoft's standards. A Linux distribution could go the Apple route and define a different set of standards a computer has to meet to run that distro, so that only computers made to run that distro could run Linux. ChromeOS is a Linux that has done this.

The commodity PC platform is basically a historical accident, where IBM used commodity off-the-shelf hardware, and licensed MS-DOS but neglected to get an exclusive license. So anyone that bought the right hardware and a license to MS-DOS could provide an IBM-compatible PC. Before the ascendance of the IBM compatible platform, you had manufacturers of general purpose PCs building incompatible machines. Now we have a market dominated by compatible machines. There's no ISO standard for general-purpose PCs that makes this happen, or any other independent standard. Windows Hardware Certification is the standard for commodity PCs.

EDIT: To clarify, this is only true regarding x86. Linux on MIPS/POWER/etc. is conforming to some other standard, not one set by Microsoft.
He wasn't saying that air resistance is currently a problem. The current problem is that the robots don't move fast enough for air resistance to be a problem. He's basically pushing the question 'Going faster is obviously good. What happens if we go really really fast?'
This is obviously field dependent. A counter example is mathematics, where the significant break throughs are often done in the earlier part of career rather than later.
As a beginner it was my editor of choice, as most of us it seems. But the GUI made me want a better editor, with the same capabilities of a GUI editor.

So, when i heard of micro i switched immediately, I just find the default copy/cut/paste and the mouse functionalities very comfortable.
Yeah, social media is just too easy to use (and free). When people take the time to make a website, they often commercialize it, then it's not really a personal website anymore.
I would suggest meeting up with real people rather than doing video chat. There is something much more satisfying about meeting in person.

When I used to work alone, I had to schedule regular social interactions to keep from getting lonely (coffee or lunch with friends, meetups, etc...)

It's important to focus on your startup, but it's impossible to do that unless you take care of your mental (and physical) health.
Maybe because you attracted people interested in freelancing, not actual freelancers.
Yes, I am aware. But weaponized drones and robots will give much more power to a future skynet or a lesser version that autonomously acts with minimal guidance which may unintentionally divert from human goals. This greatly increases the priority of AI Safety research.

Some people I know kept arguing we can simply unplug the skynet and be mostly safe (despite some damage). These AI weapons make it clear that we will not be able to largely limit the damage to the virtual world.
Most startups aren't doing rocket science and younger people are generally cheaper, doh.
Let's dispense with the facade. Younger employees typically do more for less, and are sought for their energy, flexibility and/or willingness to entertain new ideas, and not necessarily because they invent the new ideas.

It used to be that fast food chains hired teenagers because they could pay them less, and in exchange the kids got to feel like adults usually for the first time, even if the environment was dubious.

Startups are running a similar game, only the skills needed are rare enough that the price tag is sky high compared to ordinary jobs, and only because there really have been a few unicorns and the calculated risk of investment in these sorts of salaries is potentially worth the gamble.
CCC this December in Leipzig
What's key to selling? Is it to pander to customer's wants? or make something so good to make it practically a need that money means little and customers will gamble?
RESTful APIs Technologies Overview
Speaking as very-much-not-a-JS-developer: Isn't this essentially the same problem Linux package managers solve with -dev, -doc, and -dbg packages? I.e. the default install only contains the minimum necessary to use a program, and if you need the header files/documentation/debug symbols, you can just install them separately.

Is it too hard to meaningfully separate these parts of a package, or is it more of a philosophical issue?
Incremental Innovation.. yes. Also older people tend to have more power in hierarchical organizations thus that study might just show the bias of hierarchical Organisations against disrupting ideas and the power of endurance.

We have the most variation ofexperience as young ones. Nature when we cut the social navel sends us into a society where every good hunting ground and every big prey is already taken. Thus we rebel to fight for a chance or to generate a resource we innovate by leap. The youth is the only force to gain by disruption.
As explained on the website, that's why this is Luxon and not moment 3.0. It's a great approach for them to take that allows them to experiment, grow, and relieve the pressure from calls for change, without disrupting the existing community.
Mapping the Development of Autonomy in Weapon Systems [pdf]
I think you're wrong, the theory of evolution has been suffering under the oversimplification that is 'survival of the fittest', that also led to e.g. Social Darwinism, which is dangerous and completely bogus.

Evolution Darwin already knew (and even more so we nowadays know) is a complex mechanism, that includes favoritism of certain traits of species over others, which steers a species' fitness for the environment, and several factors play various roles, e.g. epi-genetics.
I for real find it terrifying. If we were sane, we'd be pushing for international treaties against this same as chemical weapons, instead we're making it happen and selling the tech to people.
Years ago I created a public TeamSpeak server to meet and talk to people with the same coding interests. It never got much attention, but it's still online at devcon5.org. It's a voice group chat where you can create your own channels, but has no video features.
My favorite is how PSP is confused with DASH, the thing that actually does remote management.
> Code-monkey Indians

I realize (because you say it below) that you're Indian so it feels ok to say this. That might be true in person, but not here. You're broadcasting to a far larger audience with far less information about your intent. In this context, subtleties with slurs (such as 'it's a self-slur too, so that's ok') aren't really possible. If you casually drop the slur in anyway, you're damaging the container that protects what little kindness we have here, so we'd appreciate it if you'd not do this sort of thing.
What did we do wrong?

Not articulating, testing, and validating all of your initial assumptions before building/launching the project?

Who did you talk to first? Are you sure there's a market of people who have the problem you're trying to solve? What research did you to to identify your potential market? How do you know how to reach that market (hint: they might not read Product Hunt)? Do you know how much they're willing to pay? Maybe you're charging too much. Maybe you're not charging enough (if something is too cheap, it can be perceived as low quality even if it isn't).

Or maybe you just haven't given it enough time yet. When did you launch? How quickly do you think people can evaluate a solution like this, decide if it's what they need or not, decide how to integrate it into their business, etc? How quick could you do the same?

Maybe you just need to run a drip campaign (you have emails from the people who signed up?). Or maybe you need some good old fashioned outbound selling... go all Glengarry Glen Ross on 'em...
As a language, yes C# is probably better. If I may grant Java a pithy defense as a C# user not as a contradiction but additional information.

On the implementation side, Hotspot blows the CLR out of the water on performance. All things being equal that is, not handicapping the Java code, bottlenecks "for realism" and other benchmark-defeating tricks.

Java is the superior serverside solution. Other than Hotspot performance, the other big selling point is Java's vastly larger opensource library selection.

I like both. I like the fat OOP space. Maintenance reasons is a huge one, I don't want to get burned having to maintain some fly-by-night's code in 10 years from a Frankenstein's creation of random JS libraries. Both Java and C# are industrial-strength designs, with good tooling and a swath of devs.

Between the two, I'd still reach for C# myself, because at this point you can have an almost entirely C# codebase from the server to the client. It's good enough in the performance and library aspects that Java holds over its head. I'm expecting the C# package to be quite complete once it adds compiling to wasm to its list. But if I made a career switch, it would be from C# to Java, and nothing else. I admire Rust and (especially) Elixir but no jobs in my area for either of those.
For me and I'm sure others one of the most important differences is immutability. This has been a big request from the community, but would be impossible to implement in moment without breaking much code which relies on the current mutability.

https://github.com/moment/moment/issues/1754
There would have been very little gluten in that bread - look at the rise. Additionally, something about soughdough reduces the effect of the gluten on those that are intolerant. Don’t take that as medical advice though...
You could always go for big brands... Sony or Sennheiser or Apple.. you get QA from buying from big brands because their name is on the line. Small unknown sellers.. not so much.
It's also a biased component. Patent-filing opportunities mostly go to senior or above engineers at larger firms.
Equity changes that a bit. Especially for founders, equity is how you capture "what do I deliver". Salary is "what do I need". It's not a strict divide, and the calculus changes as the company matures.
A Vision for Decentralised Computing
We can make it considered unacceptable and against international law. Like chemical weapons. Which still happen, but not as much as they would if the U.S were, say, planning on using them all over the place, doing heavy R&D into them, and selling them to other people. Like, you know, robot kill bots.
Thanks! Url changed from https://www.washingtonpost.com/news/worldviews/wp/2017/11/18....
It's nice to live in the country that's at the top of the global political order, it's just _our_ "enemies" that have to worry about this sort of thing.

For now. Things change.
They aren't needed during runtime though, that's what this project is attempting to clean up.
Computers can integrate data from numerous sources and sensors and respond very rapidly. Humans are optimised for a limited set of sensory inputs. When those senses can be utilized a person can be ridiculously effective. But space ships do not readily conform to this.
There is a reason protestant comes from the word "protest". The catholic church has a lot of baggage.
There's a subreddit that shares these kind of videos.

https://www.reddit.com/r/WatchPeopleCode/
This past week, I, living in country Australia, a few hundred kilometres from Melbourne, needed to help a coworker in Melbourne to diagnose something on his VM. It was easiest for us both to hook the SSH connection via a server in New York—increasing 30ms of round-trip latency to about 560ms. A terminal alone was fairly painful to use, but this is the part that I found really interesting: stdout line buffering goes from being a performance optimisation to being a significant slow-down—nay, a nightmare. Installing packages via Yarn, for example, suddenly took minutes, where it took only seconds with `> /dev/null`, because of a progress bar that kept on flushing its stdout buffer.
Thank you for all the feedback. I'll go through all of them one by one.

About validation, we launched on upcoming a month ago with a landing page https://www.producthunt.com/upcoming/sieve-pro and had over 150 people subscribe.

Maybe it's about giving it time, we only launched on product hunt 2 days ago :)

I was particularly intrigued by what happens between clicking signup and then dropping off, we had 400 out of 600 people click signup and then drop off.
Maybe it's not an honor.Why these guys hate UI? Why these great guys cannot make a great UI?
UI hard? there are tooooo many DOM js UIs. Maybe it's a shameness.
On the down side for us, decent bread gets made at very high temperatures. Those Roman ovens would beat any standard kitchen appliance by a mile. A wood fired traditional bread oven holds heat very well and gives a very even bake at high temperatures too.
Of course I have, they were what I was referring to. If we didn't have to deal with this python 2/3 schism, there's a solid chance they'd be part of mainline python by now.
Yeah, sorry about the context switch. The line for Show HN can be hard to draw sometimes. Is this a "sharing something you've made that other people can try out" post? Or just an ad? The latter would count as spam on HN?

In this case there looks to be a real product people can buy; that's good. On the other hand there's little substance to the post beyond its adness. It might have been helpful if the submitter posted a comment explaining the project and engaging discussion about it. That's usually a good thing for Show HNs.
I'm sure if you live a full life where you are constantly learning new things and having new experiences you can reach old age with a lot of mental elasticity and a wide-ranging perspective. Problem is, many people seem to narrow their perspective and close off to new experiences after a certain point, usually after they have children--at least the older people in my life do. So I suspect what's going on in the study mentioned is a bit of sample bias.

The great advantage of youth is that there are endless possibilities you can be molded into. Which is probably something SV investors look for.
Show HN: Confusing ReactJS Toggle
I noticed that too. I believe the answer is the repression of fear.

The human mind will avoid awareness of a possibility that would involve extreme psychological distress. When something is "too terrible to imagine" ... people will completely not acknowledge it.

This applies to many cognitive situations, including an individual's predictions about the future. It also applies to determining the intent of other people, and even a person's self image and memories.

What is frightening is that the same principle really makes mass atrocities possible. Psychology and history show clearly that people would rather become docile and distracted than face the possibility that they may be murdered by an overwhelming force.

BUT WHO CARES WHAT I THINK.

MY IP IS SHADOWBANNED FROM HN.
Woah, wait. DRM and the ME are not fine in theory. Secure boot is.

If the practice of installing your own keys is too hard, that's something we can fix. We can't fix DRM or ME without just removing them.
You're probably right. Sadly, the vast majority of the python upgrades probably did not require breaking compatibility. Or if they did, they weren't worth it. I understand that iterators are arguably better than lists and print should arguably be a real function, but those advantages are far too small to justify breaking compatibility.
Just one thing—please increase the font size. `--font-size: 14px` is just too small for comfort. The standard default of 16px is a good balance. (`--font-size-small` also naturally needs to increase.) Other than that, it’s a pleasant minimal design.
I've been thinking about this in a different way: what about bundling things with rollup.js? Then each package in require() would be just a package.json and an index.js. I think this might even help with performance.

Edit: lightened up (;
(not op) I live in Boston. I have 3 grocery stores (2 supermarkets, 1 Korean grocer) within half a mile of me. One is directly on my bike route home. I walk or bike roughly once or twice a week and pick up a few days worth of food. Each visit lasts maybe 15 or so minutes. When I lived in the Midwest, I'd drive once a month and make it an all afternoon ordeal. Doing it the "Boston way" is probably a little less time on average, about the same cost (actually cheaper with the car cost), and yields a far fresher+healthier diet. When I lived in the Midwest, most produce would be rotten in a couple of weeks, most meat would end up at some point in my deep freezer, and dry goods (like box/can foods & starches) were the base of most meals. Now I eat fresh greens daily, rarely eat box foods, and shaved 5 points off my BMI.
Usually I don't care about what language an executable is written in. After all, as a user I'm just interested in whether it executes or not.

But these small-software situations amaze me. Someone with a node_modules problem will have readily available sh, node and maybe python. So why golang? What could those not do, or golang can do better to such extent that it trumps availability? Similarly there's a price to pay in terms of people contributing with a fix: who is interested in pruning node_modules and will send in a golang PR?

In other words, if a dev would prefer Java (specifically chosen because it exacerbates the startup time), would it still pass as ok? Luckily golang can compile to binaries but that implies you give up availability on the other end, now being confined to someone compiling and publishing on a regular basis, as opposed to just pushing a fix commit to a git url.

None of the above would be of importance if this would be a personal-quality repo with a note: hey i did this at 2am out of frustration, i chose the tools that i knew best, use it at your own risk, opensourced to share knowledge and to access it from my own projects, not as a "productified" software.

EDIT: I would much prefer a commenter's solution in sh for the reasons above but also readibility: https://gist.github.com/gpittarelli/64d1e9b7c1a4af762ec467b1... :clap:
The Leap into Quantum Technology: A Primer for National Security Professionals
https://github.com/tj/node-prune/blob/20703f18e9a7996683f1b8...:

// Copied from yarn (mostly).

I infer that TJ used `yarn autoclean` as a starting point for this.
I think it's naive to think their primary focus will be collateral damage. Is that really the focus in any war at all?

https://www.vox.com/world/2017/11/16/16666628/iraq-nyt-casua...

And that's just the targeting of the drones themselves. But how accurate is the intelligence targeting? Post-Snowden we found out that they were killing people mainly based on what SIM card the targets carried with them.

Plus, they consider any male that is killed and above 16 years old as a terrorist. It's harder not to be "accurate" when that's your definition of a target...

Also, you're forgetting one aspect of this. The cheaper the tech becomes, the easier it will be used. Just like we now kill 100x more people with drone strikes that we did with airstrikes, in the future we may be kill 100-1,000x more people with automated drones, because it's so much easier to "get rid of the baddies".

Do you actually think they'll hire 100x more people to operate those machines and "have final say"? Yeah, no way that's how they'll think about it - unless we make them think differently about it and not to allow the automated kill machines to ever be built/sent.

I mean, given the type of politicians the U.S. government tends to have these days, which option do you think they'll choose? A 10-year dragged out war against a group like ISIS, or "just sending 10,000 automated drones" into multiple "hot areas" and "finish the job within a month"?

Can you not see how their logic would go, and that we'll actually need a lot of people to oppose that type of thinking to ensure it will not happen? But will there be a lot of people to ensure that doesn't happen, if say a terrorist group takes out the White House? Or will everyone think "those 100,000 people all killed automatically by the drones deserved it for destroying our White House!!".

Heck, Trump already asked the military "for the biggest bomb they can send" - a bomb that was built but never used before - and it wasn't even a situation of the US being under huge immediate threat at the time. It was mainly done for PR purposes for Trump to show how macho he is and how he "gets things done." The worst part about it is that the media seemed gleeful about it, rather than condemning him.

I think it would be best to ensure the machines are not built in the first place. There are too many trigger-happy people that would send such drones out.
In the legal profession, you start off as a grunt, but with gray hair comes more competence, respect and money. Tech is definitely a better choice for the first 5 years in career, but I'm not sure long term.
Startups work because nobody in them already knows their value.

I'm now over thirty and expect a big desk, two computers, free fresh coffee, free lunch and a real paycheck. Can't build a start-up with that kind of requirements.
Yes absolutely: this very magic is precisely what is so horrible and imho a rabbithole of insanity. It is CORBA resurrected with XML.

In my data oriented mind, the primary thing that matters is the data that is sent, the second is other semantics like idempotency.

Neither SOAP nor XML solve or helps:
there might be no wsdl bindings in your language, or they are badly implemented (true in my experience).

XML make people nest structures where it could have been flatter, SOAP even more, and annotates everything whithout a need for that.

This cost for no reason but to entertain the CORBA like pipe dream, or should I say nightmare.

We just resorted to pulling out data from xml
with xpath. And more or less template the response back, no wsdl and very simple.

But why inflict this pain on your API users?
Wouldnt it make more sense to bundle, minify and treeshake your package than to delete unused files in node_modules? Tree shaking will remove unsused code even from files you are using.
Well to be fair “GB” could refer to either prefix.
> handy looking stuff like the SustainedLowLatency GC mode

Don't forget "server mode" GC. I have a long-running, memory-intensive console app which was taking about 45 minutes to process a typical batch of data. With some profiling I discovered that after the 20 minute mark, most of the time was spent in GC. Some of the classic optimisations (classes to structs, new list to list.clear) helped get the processing down to 30 minutes. After some more Googling I discovered and tried server mode GC. Suddenly it took less than 13 minutes.
No disrespect to TJ (he did many awesome projects I use almost daily), but wouldn't simple:
'find node_modules -not -regex ".*.[js,json]" -delete'

do the same job? Why project in go?
Best and most telling part of the video: "trust me, these were all bad guys"
Shostakovich is a 20th Century composer, died in the 1970s, so at least as far as he is concerned, he wrote music with today's tuning systems.
You can't always do that (native modules, other non-js assets..)
Your comment is unclear.
”It was not immediately clear what type of calls the vessel may have tried to make but submarines that are stricken underwater can float a location beacon known as an EPIRB to the surface that can then emit emergency signals via satellite.”

Makes me only very slightly more optimistic w.r.t. the chances of finding the crew alive. Being military, their normal objectives would include “don’t let anybody see you”, so they wouldn’t use such a device unless they were in truly dire trouble.
Do you have an example of what you're talking about?