skysight-inc/HackerNews huggingface dataset:
Domain Age - They've been around forever with tons of materials.

Quality - good enough for most things. The newer stuff is not that bad and usually more practical(read quicker to grok for someone in a hurry) that the more thorough MDN docs.

Dirty trick - association with w3 standards body (none in reality)
I'm a big Rust fan and have been using it for three years at this point. However, I read nicoburns's original recommendation as "It could be fun and intellectually rewarding to learn Rust", not as something they suggested because it's directly applicable to a lot of projects.

Personally I would say learn it because it's one of those languages that changes how you think about programming as a whole and learning it will make you a better programmer in every language.

That said, I think Rust shows the most promise in a few places:

1. Pretty much anywhere you'd historically use C or C++.

2. WASM

Because Rust can expose C style FFIs you can use it to speed up hot code paths in almost all scripting languages(Python, Ruby, PHP, JS etc). This can be very useful because it allows you to keep most of your code in the scripting language that you and your collaborators are familiar with, while benefiting from Rust's strengths too.

For WASM I think Rust is currently the best choice, it has excellent tooling to work with the web, it's by far the most approachable suitable language for someone who already knows JS, and it doesn't have a big runtime or GC which makes many languages non-starters for the WASM usecase.

Some people would tell you it's a good choice for general purpose backend and there is an ecosystem around that, but I would say if that is your goal Rust offers nothing that Go doesn't do better or at least as well.
Do you mean for a single job/pipeline? This wouldn't be possible at the moment. Our current focus has shifted from Beam a little bit - as we found out the beam threading model didn't play nicely at all with Jet's green threads (there is no way to distinguish between blocking and non-blocking calls).
Would a system that allows the drivers to "set their own pay" and in which Uber dispatches drivers with the lowest rates follow the law better? This would clearly be a race to the bottom (the pay would probably be even lower than what Uber drivers get today). Is that a preferable outcome?

I also object to this characterization of consent.

> The only freedom an uber contractor has is "when to work".

How is this not complete freedom? Loads of contracts out there specify the rate that the contractor will be paid, and both parties are expected to uphold that specified pay. Are those contracts no longer valid? In some cases with written contracts, the pay is specified as a non-negotiable condition from the paying party, and the "only freedom" the contractor has is to take it or leave it. Is that a violation? If a contractor never actually gets hired under a contract for which she sets her own rates and all of the other "freedoms" supposedly necessary for forming a contract (in CA), is she being oppressed in some other way?

No one is holding a gun to Uber drivers' heads forcing them to drive. They seem to be doing it voluntarily (this seems the case for every one I've met). Insofar as this is their only option, this is not a problem of Uber's creation, but of the overall political economy. And that, after all, is GP's point.
So, I don't really know the context of the stuff you're writing about, if you would please indulge me...

> Watching Mozilla leadership drive Mozilla into the ground over the last 8-10 years has been like watching a bus accident in slow motion.

I honestly am not aware much of that.

> FirefoxOS anyone?

I can't tell if you're unhappy they started that project or unhappy they stopped it. I'm guessing you're unhappy, so I'm going to go along with the guys that were involved on that project for the rest of your post.

I am curious though, since you seem to know so much about Mozilla driving itself into the ground, do you know the resources that were spent on FirefoxOS?

> The only benefit Mozilla now provides is a warning to companies that place how liked and popular employees are over how skilled and hard working they are.

I know that Andreas Gal was disliked, but how was he unskilled and what did his position have to do with the nature you're speaking of?

> Mozilla has collected such a large group of well behaved and well liked underperformers to an absurd level like no other company in history. This is no more obvious than the woefully under-qualified and perennially under-performing leadership.

How did you asses that Andreas Gal was under qualified and under performing?

> Someone please explain to me how Mitchell Baker continues to have a job?

Mitchell Baker is one of the oldest closely related employees to Netscape, Mozilla etc. She is very much the original culture of company. Her particular focus is the overall business aspect of operating the organisation rather than the technical. The technical work would have been people like Andreas Gal.

> How is Mozilla still paying this person millions, yes millions, of dollars?

That's not her sallary, that comes from compensation. Compensation is based on looking at what other similarly sized companies, usually in the same sector are paying based on similarly skilled people. Companies do not want to lose their CEOs etc. What might suprise you is that she's being paid at the lower end of the scale, and this is because she's a CEO sourced internally.

If Mozilla were to replace her with an external CEO, they would likely end up needing to pay vastly more. The compenstion paid is usually pegged to performance. While the company might have not done well as a whole, there are likely things this person has navgiated the company through that you did not see? But, if you did, please share.

> Pocket?! You are going to save Mozilla with a glorified bookmarking app?

Mozilla is following a common technique to help bring stability to the company when one or more revenue stream starts struggling or drying up -- It is diversifying income. Mozilla appears to be a very R&D sort of company, so they seem to be doing what you see companies like Microsoft Garage or Alphabet do and try to create their own 'start ups' without the company bit to try to innovate new products. Hence where FirefoxOS came from.

Many people originally scoffed at the idea of Apple doing a phone.
This is if your components are in the app’s codebase itself and not in a shared components library. The workflow there gets a bit messy IMO since you probably need to then maintain an entirely separate RN app just for the storybook in that component library’s codebase, which leads to a decent amount of redundant work when upgrading RN versions.
Medication has been truly life-changing for me. The ability to actually follow through on things within a day is amazing.
I use https://jsonformatter.org/json-parser sometime to parse json and to validate.
After link chasing from that Tweet, this appears to be the underlying quote:

> Here's what I mean by mitigate: we ask our executives to accept a discount from the market-based pay they could get elsewhere. But we don't ask for an 75-80% discount. I use that number because a few years ago when the then-ceo had our compensation structure examined, I learned that my pay was about an 80% discount to market. Meaning that competitive roles elsewhere were paying about 5 times as much. That's too big a discount to ask people and their families to commit to.

https://answers.thenextweb.com/s/mitchell-baker-aGY62z
Or you can always remove the keys... and a can of flat black spray paint.

Same effect - but with less sanding.
This is how we use it and it works well. Other teams are also free to use whatever else they want and if we need an "overview" it's pretty easy to upstream certain metrics elsewhere (say, a centralised system run by ops) to collate together.

Being able to also control which metrics are important to my team vs the wider team is a BIG bonus of this sort of decentralised system.
True, but to be fair, that is a huge freedom, and one many people want or need.

Yes, driving Uber is a shit job, but for many people it is far better or more compatible with their lives than waiting tables or working retail, which are the realistic alternatives for most Uber drivers.
> With the caveat that the source is a Twitter thread, if this turns out to be true it is increasingly looking like the end of Firefox and Mozilla. Earlier today, a separate Twitter thread was posted that claimed the whole Servo team had been let go.

It's pretty clear Mozilla was never planning to have Servo completely supplant Gecko. Their approach has been to treat Servo as a research project and then fold technologies (like Rust and Quantum) into Gecko as appropriate.

Through that lens, you should ask yourself if it makes sense for Mozilla to fund an R&D effort like that given they're operating on a shoestring (especially with at least 75% of their revenues about to evaporate thanks to the Google deal not getting renewed).

I think you could argue either way, and I don't think I have a strong opinion. But I think your framing is overly hyperbolic and doesn't reflect what Servo actually was and how it fit with Mozilla's overall strategy.
When I took typing in school back in ~2001 we still did it on typewriters and we were not allowed to use correction tape. Having a sheet of paper fixed over the keyboard so we couldn't see it was also mandatory. That almost everyone had access to a computer at home did not matter, but I'm pretty sure most people who took the class became proficient typists in the process, I certainly did
Hot damn. So that’s what that setting does. I thought it just triggered zombies or something, never gave it a second thought.

This is the explanation I was looking for. I wish you all the karma, thanks!
Would it have changed outcomes for you as an entrepreneur?
Or just rearrange the key caps. IME, that retrained me much faster than blank keys.
I also would call Rust the new normal for fast secure code.
I'm not disputing that they proved their point, but this is triggering one of my pet peeves about common misunderstandings of Morse code.

Timing is critical in Morse code. You can't just write out a bunch of dashes and dots to transcribe it without clearly transcribing the rests between dots and dashes as well. They haven't given us the rests at all, so all the info they end up having is:

dot dash dot dot dash dot dot dot dot dot dot dot dash dash dot dash dot dot dot dash dot dot

And that can be interpreted in any number of different possible ways besides "REDHANDED". E.g. it could also be "AU5EWRFE", or any of thousands of different interpretations (actually probably a lot more than that; this would be a fun programming problem). They should have used a binary encoding; 22 bits (all they have given us) is not enough information to uniquely encode the string "REDHANDED". Once you include the short rests that are needed, we're talking 44 binary bits or 22 ternary bits. And if you want the long rests to distinguish properly the spaces between words, then 22 ternary bits won't do it; you need the full 44 binary bits.
React95: Windows95 UI components for modern React apps
And an easy way to tell is there is no section in the post on what the downsides are to picking Rust.
The HHKB Lite is totally different and pretty awful, regular HHKBs are great though! I used a Lite a few years ago and it had some of the worst rubber domes I've ever felt, nearly every key felt like it had a different actuation weight. The arrow keys were especially bad.
> Lockdown with family in one’s dwelling isn’t prison

There's literally a punishment called "house arrest".
Lithographic printers already exist and are now cheap. You are likely reading this comment through a photomask right now :)
Then you’ll be limos.com in real time.
The planned parts of DC and SLC are the old parts of the city. The rest of those cities were not planned in the same way, and it shows in the haphazard geography and zoning. (For example: why does SLC have 24/7 factories a block from housing?)
> This kind of implementation is actually quite concerning, because it means you're punting through a language which is notorious for its heavy reliance on undefined behavior, and there is no way to opt out of undefined behavior in some cases.

if it were a new project I'd agree, but if there's an existing C codebase, it already contains all these UBs and the goal of the rewrite is to grow a formally-verified critical core functionality in ATS that would still inline the rest of the project intact. This way the formally verified part of the project can grow naturally through small iterative steps without major disruptive changes to the tooling and supportive infrastructure.

People who are familiar with C can acquire basic ATS patterns pretty quickly (within a month or so), and the same is applicable to those who are familiar with ML-family languages.
I think the parent means that she failed at this. At the very least, her salary went up while Firefox market share went down.
I've heard founders say this too. The mentality is "look, you'll end up giving away 20% of your company on the round anyways, so you might as well get more $$$ for that 20%". As if the % is fixed and immovable.

In my own experience, this minimum % ownership target is a very real issue and bar to jump over for most "proper" Series A VCs. At least the ones leading the round.

If I was in that position, and it was a great fund, it would be very hard to imagine saying "no, I'll value my company less, and take less $$$, for the same dilution." Human nature IMO basically favours taking more $$$ every time ONCE % is fixed.

However, Aaron might say that the best companies can easily push back on that fixed % approach, which is the true issue here. And that's a good counter point. But many of us, even as YC-backed companies, don't know how to effectively push back against that dynamic.

For me, out of the 5 Term Sheets I got for our Series A, I think all of the funds involved had a minimum % ownership target. Hard to negotiate around that. Normally if there is a term you don't like, and you have multiple sheets, you can just play them off each other. But it seemed pretty universal in my admittedly narrow experience.
The rebound didn't go all the way back up to how it was before.
Optimising for a good valuation (over a good business that you own lots of) is missing the point.
In the Timescale Cloud portal, once you create a database, it's one-click "upgrade" to move between any of these configurations, and it happens with ~zero downtime.

That's also true for multi-cloud migration, you just select that you want to migrate from a 100GB instance on AWS to a 200GB instance on GCP, and the migration happens behind the scenes.

(Technically, it does so by spinning up a replica of the new configuration / location, and continuously migrates the database, including any online changes happening concurrently. Then, at the last minute, it "swaps" over control from the primary to replica, and then retires the old primary. This is all hidden behind DNS too.)
That doesn’t say it won’t be renewed, just that it’s currently not renewed.
> I'm an adult, if I want the money isn't it strictly better than I have the freedom to cash in on my human resources?

Yes.
I am 100% ok grunting through a lockdown if it shortens the duration of this awful fucking pandemic. The current soft restrictions with no clear endgame is 1000 times more shitty than having to hole up in your apartment knowing that it will end all the other restrictions sooner.
aahhhhh..... yes, they warned us about this so much in university that I've had "talk to stakeholders to really understand the nature of the problem, then keep observing" firmly lodged into my professional identity.
Is ATS really suited to being an industrial language? How do its standard library, build tools, and library ecosystem compare to Rust's?

Admittedly, if you're switching from C, you start with a pretty poor story about all that. But at least that story is widely and thoroughly understood.

ATS has an optional garbage collector. It seems the standard library has two implementations of each container type, one which uses GC, and one which uses linear types, so does not need GC, but is more demanding to use. That is pretty cool! What is the situation with other libraries? Is there a convention of assuming GC can be used, or that it can't, or of supporting both?
With blank keycaps there's no way to cheat, it forces you to learn everything on the keyboard you use regardless of how often it is used.
I have touch typed most of my life and switching to blank keycaps 5 years ago forced me to master all of the keyboard, specifically the less used keys.

Its also fun watching people try and type on your blank keycaps - they are all almost instantly lost at how to even start typing.
Thanks, I'll send him a message. :)
Is that not normal? That’s been my typical experience with using Uber/Lyft outside of urban centers.
Thanks - at any given round, dilution is driven by how much money the founder agrees to take. No outside party can force a founder to take dilution, it takes an agreement on both sides.

While VC ownership targets are part of their business models, founders don't actually have to agree to meet them. From what I've seen, those targets are far more flexible than anyone admits at the start of a negotiation.
A new Node.js learning resource
Millions of Android phones could soon start detecting earthquakes
Is it worth the effort to write a "X should switch to Rust" post that ends with "but I personally don't have the appetite to do it"?

Migrations of this size aren't not done because they're technically bad ideas, but exactly because they're expensive, messy, and few people have the appetite or funding to do it. Proposing a solution to that is more interesting that just saying "switch to Rust!".

Also, I don't know much Rust (still on my PL bucket list), but usually when I dive into a more detailed analysis of such a migration the most relevant parts are around how much unsafe code will be required and whether or not integrating with the existing codebase has to be fine-grained or can be done in larger modules like Rust recommends.

I would naively guess that a VM would have lots of unsafe code. Are there any investigations on whether the recent vulnerabilities would have migrated to safe or unsafe code?

edit: mea culpa. I didn't read the second to last-paragraph closely enough, which at least proposes a modularized way of doing this with device emulation being written in Rust in separate modules.
The main difference on Timescale Cloud between dev (starting $115) and production is just the resource availability and slightly longer PITR recovery period for non-dev options. Both offer same full TimescaleDB experience, console, ability to upgrade/downgrade, fork your database, etc.

If you do want a lower priced option, we actually recently also released a second managed cloud offering in public preview, Timescale Forge: https://timescale.com/forge.

Timescale Cloud provides great flexibility with multi-cloud and 75+ regions, security conscious options like VPC peering and SOC2/ISO/HIPAA compliance, and a more traditional DBaaS Experience.

Timescale Forge is a innovative platform with capabilities like decoupled compute and storage (so you can select yourself the exact configuration you want, starting at $49/month), instant pause/resume, native support for our Prometheus integration, and more coming...
>40 hours according to the California Department of Industrial Relations and 30 hours according to the Affordable Care Act.

So uber can avoid this requirement by only allowing drivers to work for 40/30 hours per week?
There may not be an explicit section, but the post certainly talks about how it would be a mistake to rewrite the code, and gives reasons.
What about the third opinion timing and luck.

You are exposed to the right sets of ideas at the right time and your brain through random chance happens to take a particularly fruitful paths to explore the ideas creating an exceptionally useful mental model. You have emotional preconditions that cause you to process this success in a helpful rather than a harmful way. This feeling of success and excitement causes you to spend more time daydreaming about the subject, slowing building a reservoir of powerful and useful mental patterns. Someone can daydream 10-16 hours a day for 14 years, but it is very hard to find someone that can study a subject they don't like for 8 hours a day for 5 years straight. I would argue that studying a subject is less likely to result in new ideas than day dreaming.

Due to having an environment to grow these ideas, not being run over by a car, having the money to pursue schooling, and exploring a field which is undergoing a revolution at the time you could up 'a genius'. Would anyone outside of Academic Physics know Feynman's name, if he entered Physics in 1995 when much of the low hanging fruit had already been harvested?

One could argue that Grothendieck is a counter example to this argument because he grew up in very harsh conditions that for the most part actively suppressed his learning. However I would claim Grothendieck for the luck and timing argument for four reasons:

First the trivial argument, if Grothendieck had starved to death while hiding from the Nazis as a child no one would name him as a genius.

Second, when he started college he was doing very poorly and he almost gave up, but he had mentors and an early success that enabled his later successes. What if he had gotten a cold that stopped him from that early success. It seems likely that given different friendships in college he would have dropped out and never been heard from.

Third, he was very interested in political movements and dedicated much of his life to it. However, he was not particular good at this. If he had an early success in a political tract he wrote, it likely would have led him into an area that he would not have succeeded in as much as Mathematics.

Fourth, French Mathematics at the time was undergoing a revolution because so many of the older Mathematicians had died in WW1 and WW2. This created opportunities for younger Mathematicians to rapidly advance their careers and these younger Mathematicans were critical to Grothendieck not being sidelined.
IE was largely a defensive move to prevent Windows from becoming irrelevant as a developer platform. It served its purpose and then was left to languish.

Chrome was largely a defensive move to prevent Google's ads from being disintermediated. It continues to serve its purpose.
From Stock Market side project to micro SaaS
Control offering free next gen upgrade with a slight catch
The data may look like crap (to you) but it’s better than absolutist remarks and anecdotal allusions... and as this thread so aptly shows, there’s been a range of reactions, some even favourable.
That is why linkers are relevant.

Tiny Go, D and AssemblyScript all manage small enough download sizes.

Then just like with native apps, one doesn't necessarily need to download everything at once.
If you have a cheap old keyboard, try popping the caps off the keys and rearranging (leave F and K alone). IME that's much more effective than blank keys (the information is not merely missing but wrong in a way that's immediately obvious).

I'm not sure this will work for all types of keyboards, so make sure it's one you're willing to sacrifice... but that's a lot cheaper than the fancy blank ones and possibly cheaper than a can of spray paint. Also, it's probably not going to work very well with anything ergonomic.
One additional point. If you have existing investors who have pro rata rights, the larger the check from the new round lead investor, the more existing investor money is also being put in. And since all VCs are basically in a "I want to put as much capital into winners as I can", the insiders are likely OK with larger rounds / valuations in general, since they get to place more $$$.
Periodic Table with Origin of Elements