skysight-inc/HackerNews huggingface dataset:
"throwing away" and "jumping on the bandwagon" are two sides of the same problem: lack of forethought.

If you take the time to adopt a technology and understand the pros and cons thoroughly you will not be doing any throwing away. You may end up not adopting the tech if its cons are not acceptable in your scenario but you wouldn't be adopting it then throwing it away.

On HN, we see two extreme patterns:

1. Why we at $FAMOUS_COMPANY Switched to $HYPED_TECHNOLOGY https://saagarjha.com/blog/2020/05/10/why-we-at-famous-compa...

2. Why we dumped $HYPED_TECHNOLOGY (https://solovyov.net/blog/2020/a-tale-of-webpage-speed-or-th...)

It's good entertainment (for some) but in the same way that mainstream media manufactures drama.

:/
> People don't want to say "sure, I'm around" and then 5-10 minutes later say "sorry, I don't have experience with that".

Yes, if only humans could outsource such desiderata to some kind of specialized "engine" that could produce human language sentence given a set of explicit data and instructions.

Would this be the right forum to ask about how to design such an engine? Seriously asking because it doesn't look like anyone here has experience with solving such a novel problem.
I don't know.

The reason I tend to do this is because sometimes I have problems with figuring out what my issue actually is, and that I might be running into an XY problem. For these reasons I prefer to engage in a synchronous form of communication.

That doesn't mean that I expect someone to commit or that I won't respect the person's boundaries when they refuse to help for whatever reason.
And you think that percentage will get lower? Please. Tech will only get larger in the long run.
^^^ this

That article is well worth a read. I now am using PA in this mode.
Glad to see some agreement there. I'm interested in building an ECS-based approach for a UI system at some point. The Yoga layout engine (implements flexbox -- https://github.com/facebook/yoga/tree/master/yoga) seems to actually be pretty amenable to just incorporating as a `Layout` or `Flex` component, then you could have components for platform-specific renderings (eg. `iOSTextInput`, `AndroidTextInput`, `DOMTextInput` in wasm, ...) that could read from cross-platform common components (`TextInput`). A core aspect would also be a `Hierarchy` component that just has a parent entity id and a list of child entity ids (that it keeps in sync properly). Then bind things to JS and allow you to code it from React, while still being able to eg. run an animation thread for some specific animations that just queries and reads/writes the `Layout` and `AnimationSpec`s etc. Interesting talk re: data oriented design for a webby animation engine here actually: https://youtu.be/yy8jQgmhbAU?t=620
> the way of managing things through gameobjects, serializable components, and the scene hierarchy UI is very beneficial when you have non-programmers working on your game with you.

honestly it's extremely useful even if you're an experienced programmer working alone. Being able to pause the simulation, move some objects around in space, and then resume the simulation is extremely powerful. Typing out the coordinates into code would: be ridiculously tedious -and- force you to commit to disk (by writing the files) the changes to something you really only need in memory. Being able to play with the state of the simulation by hand is extremely powerful.
Anyone else interested in filing to go public today?
> gatsby-plugin-no-javascript

Thank you for mentioning this! I’ve been on a passive search for exactly this: the ability to use React and generate a completely static site without even the possibility of JS at runtime.
From my experience of shipping a few AAA games: a universal game engine will always be suffering from trying to balance efficiency vs universality.

It's not a big deal to write an OOP engine where you just insert objects into a scene graph and each has a callback to draw itself, write a whole library of different classes for all kinds of purposes and ship it. The problem is that it's going to be much slower than a game written from scratch by a semi-competent programmer.

It's also not a very big deal to write an extremely efficient engine that will render, for example, streaming landscapes very fast and in great detail but won't render anything else nearly as well.

It's believed that neither of these would sell well even though id software has allegedly made much more money selling their specialized maze shooter engines than selling their maze shooter games. Though probably nowhere close to the money Unity/Epic makes.

Unity/Epic try to make an engine with OOP APIs in the front and optimized pipelines in the back. This is very hard and this is why they: a) don't have much competition an b) are not very good.

In my opinion, the only threat they both face is some yet unknown universal rendering technique appearing and making both obsolete. Till then, they will always have a customer base of studios who do not know/want to write their own game and not satisfied with naive OOP engines (and there used to be hundreds of those, even DirectX had one built in, called "D3D Retained Mode").
Take a look at the hey email client. It's built by basecamp--the guys who created rails.

As for web app vs web page--it's a very blurry line, and it's rare that I end up building something where the entire site could be considered a web app. Usually only some small pieces of it demand enough interactivity to bother with the complexities of using a UI framework, and for that I wrap a small React or a Svelte app in a div and throw it on a page within the larger site.
Yeah, what is going on at Asana?

R&D costs outpacing revenue in the year before IPO really surprises me (from ~54% to ~62%).

For comparison, Atlassian went from ~38% to ~36% in the year before IPO.
Amwell S-1
> We decided, you should be able to share this stuff, because it’s interesting

Interesting, because this is main reason I don't like Venmo, and prefer PayPal, but everyone seems to want to use Venmo. In my social circle, many people have expressed similar sentiments.

I think the main thing they hit is being able to pay your Facebook friends by entering their name, before Facebook had Facebook Pay. Come to think of it, it would have been much wiser if Facebook acquired them instead of rolling out a competing payments system.
What is the source of "Btrfs requires a regularly run administrative task...".

No file system should require this kind of regular hand holding. If it does, it's a bug, and needs to be reported and fixed, not papered over with user initiated maintenance tasks. It is acceptable to have utilities for optimizing the layout from time to time, but they should be considered optimizations, not requirements. If it becomes required to use them as a work around, that's both suboptimal and neat. But there's still a bug that needs a proper fix.

In the case a workaround is needed, it's recommended to do targeted filtered balances, not a full one. A full balance isn't going to solve a problem that a proper filtered balance can't.
my guess is that a detailed account of the consumer goods you have purchased - including possibly the device upon which you typed out and submitted this comment to this web property - would indicate otherwise
Maybe even more just these 5 are on HN homepage...
You are paying Shopify for discovery and the usage of certain APIs (such as payment APIs etc).

Otherwise it’s possible for someone to integrate your stuff into their store even outside of the Shopify store (by integrating JS snippets for example).
But the smart people get networked into powerful circles. Lots of smart people get nowhere without having connections to people who control the money.
Sometimes maybe. Other times you have this story https://www.latimes.com/california/story/2020-07-16/qatar-pr...

Ultimately it reinforces a culture where influence can be passed to children.
"Well-well look. I already told you: I deal with the god damn customers so the engineers don't have to. I have people skills; I am good at dealing with people. Can't you understand that? What the hell is wrong with you people?"
You also don't want to just target the largest number of users, but the largest amount of users who are willing to pay for your plugin. I'm not familiar with the demographics of this particular market, but perhaps it's akin to iOS vs Google? Even though the latter has a hojillion users, app developers make way more money on iOS.
I'm a grad student in biophysics - even if I wrote perfect code, it would almost certainly go obsolete in 10 years because the hardware that it interfaces with would go obsolete.
Not a founder or anything like that myself, just someone with a lot of work to do who had depression in the past. I agree that consistently working out helps a lot as well as giving yourself tasks to do. You can use the good times to try to find a higher purpose for yourself, that's in my experience the best long term solution.
We've been using their SaaS version for about 4 years now. Maybe a couple of hours of downtime during that.

Unfortunately GitHub has been going down for multiple days this year, they've definitely outpaced our Artifactory instance in terms of downtime.
We have tried to switch over to CodeArtifact but it doesn't support as many repo types as Artifactory. :( We use generic type repos a lot.
maybe, but probably not imo. the people who built my macbook are exploited, but i need it for work.
> but switching to a different ISA in the datacenter will continue to be an uphill battle.

It really depends on what kind of stuff the datacenter runs.

I know of datacenters where almost all the code running is Java. For those kind of datacenters, so long as JDK supports ARM (which it does), I can't see why it would be such an uphill battle.

The uphill battle is really for sites who run lots of closed source COTS software, especially that which is written in C/C++/etc, where moving to ARM needs support from the vendors and the vendors might hesitate due to the amount of work involved. There are sites where close to everything is either open-source or else developed in-house in managed languages (Java, .Net, Python, Ruby, PHP, JavaScript, etc), and those sites are likely to find it a lot easier.
I took 6 months off after a bad case of burnout and I think you are spot on at 1 year. About 6 months after going back to work (and clearing my plate of a lot of superfluous BS) I finally felt like I was beginning to hit my stride again. It was a big financial hit, but in the grand scheme of things it would have been far worse on my long term career prospects had I not taken that time away. Six months was, in my opinion, the bare minimum for the kind of burnout I was experiencing.
What do you think about Trello?
Any time you vote a comment, that's state as well.
Illustrations from James Sowerby about mineralogy in Great Britain and beyond
"hey, can you do me a favor?"

"Hey, are you free on Saturday?"

These kinds of questions are what TFA is getting at. These questions are socially awkward and unaware.
What you wrote comes across to me as a false dichotomy.
There’s not just _perfectly crafted_ and _zero-effort,_ there are infinitely many nuances between those extremes.
No one expects perfection, or formally rigorous problem descriptions. People do expect a _reasonable_ amount of effort, no less but also not much more.

Reducing effort to near zero out of spite (or whatever your motivation is) doesn’t feel constructive. Why not make an honest, good-faith attempt insteas to help others help you?

Something like:

“I’m trying to do X. Here’s my attempt but it doesn’t work. I’d expect my code to run successfully but it prints ERROR instead. What does the message mean and how do I fix it?”

goes a long way already.

Bonus points if you minimize your example and make it self-contained.
(Note that I didn’t say “spend an afternoon polishing your example.” Just spend a couple of minutes deleting lines of code until you feel it’s small enough to be useful.)
NTDLL is only stable if Microsoft likes what you're doing. For example, Microsoft culture is super biased against fork() or any creative use of virtual memory. There was, for decades, a sort of a hush hush fork() workaround in NTDLL that people thought was stable. Then some Sunnyvale startup called Crossmeta built a product to capitalize on it, Microsoft rolled out a security update, and poof it's gone. They ignored all the documented warnings saying "if you use NTDLL be sure to have fallback!" So think twice before messing with Redmond.
Super easy to run a docker cache proxy:

docker run -d -p 6000:5000 \
-e REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io \
--restart always \
--name registry registry:2

That's it. Now fetch docker images from the IP that command is running on. Taken from gitlab: https://docs.gitlab.com/runner/install/registry_and_cache_se...
No he is saying the other one is overpaid
Maybe someone can word this statement in a way that actually describes the problem better for someone not as well-versed in the ins-and-outs of funding in academia?

The Epstein affair brings to light a much larger problem: it undermines the integrity of the research enterprise when individuals can pick and choose lines of inquiry that appeal to them simply because they can pay for them.

People funding research that interests them seems like a pretty innocuous statement by itself. Sure, it's connection to Epstein is blatantly problematic, but if you remove him specifically from the statement, what is the problem being highlighted?
Current production cycle. At the end of a Nvidia production cycle for a gpu iteration, their gaming sales numbers historically decrease before their new card series is released. I'm not sure about the factors at play that lead into that, but I assume less marketing, lower availability, and high market saturation.

The point of my first comment is that the timing of this breakdown doesn't encapsulate the full picture, and getting a handle on their relative numbers would mean looking at a few cycles over a longer period. I agree that they have "nowhere else to go but up", but the comparison in the article listed is a bit shallow.
If you don't have to build a webapp just use Webflow
Shameless plug: check out my book (in preparation) available in ebook format here: bit.ly/sml-book
> Basically, the constituency for retaining most existing means-tested benefit programs is left-wing opponents of UBI/NIT. But the right-wing supporters of UBI, left-wing supporters of UBI, and right-wing opponents of UBI together are almost certainly going to be a bigger block.

You forgot another voting bloc: beneficiaries of the current welfare systems, who might well get less money from UBI than they do from the current systems.
Is there a centralized place that we can track all the upcoming ipos?
There is something I need to add, it is a subtle but important point:

Non-determinism can be caused by

a) random seeds derived from hardware, such as seek times in a HDD controller, which is fed into pseudo random number (PRNG) generation. This is not a problem. For debugging, or comparison, it can make sense to switch it off, though.

b) data race conditions, which is a form of undefined behavior. This not only can dramatically change results of a program run, but also invalidates the program logic, in languages such as C and C++. This is what he blog post in "lockdownskeptics.org" suggests. For the application area and its consequences, this would be a major nightmare.

c) What I had forgotten is that parallel execution (for example in LAM/MPI, map/reduce or similar frameworks) is inherently non-deterministic and, in combination with properties of floating-point computation, can yield different but valid results.

Here an example:

A computation is carried out on five nodes and they return the values 1e10, 1e10, 1e-20, -1e10, -1e10, in random order. The final result is computed by summing these up.

Now, the order of computation could be:

((((1e10 + 1e10) + 1e-20) + -1e10) + -1e10)

or it could be:

(((1e10 + -1e10) + 1e-20) + (+1e10 + -1e10))

In the first case, the result would be zero,
in the second case, 1e-20, because of the finite
length of floating point representation.

_However_... if the numerical model or simulation or
whatever is stable, this should not lead to
a dramatic qualitative difference in the result
(otherwise, we have a stability problem with the model).

Finally, I want to cite one last paragraph from the post on lockdownskeptics.org:

> Conclusions. All papers based on this code should be retracted immediately. Imperial’s modelling efforts should be reset with a new team that isn’t under Professor Ferguson, and which has a commitment to replicable results with published code from day one.

> On a personal level, I’d go further and suggest that all academic epidemiology be defunded. This sort of work is best done by the insurance sector. Insurers employ modellers and data scientists, but also employ managers whose job is to decide whether a model is accurate enough for real world usage and professional software engineers to ensure model software is properly tested, understandable and so on. Academic efforts don’t have these people, and the results speak for themselves.
It may be general resistance to a concept. More and more services are becoming subscription based, so 5$ here, 5$ there and the cost creeps further.
Amazon has been putting their own chips into systems for years, after they bought Annapurna Labs - they have hardware virtualisation support in their network and storage chips, and now their own CPU. This does not seem to be a short-term tactic.
I disagree. It’s Boolean and flat (there is neither sequential nor nested logic around the state). It does recurse for each sub thread, but only in the case where there is no state. There’s also no business logic built around it, only display logic. It also is updated from exactly one location in the application.

That said, it’s a very simple and effective design. It’s an excellent program. But it’s not a fair comparison against other applications which, for one reason or another, need significantly more advanced state.
A seasoned software developer encountering scientific code can be a jarring experience. So many code smells. Yet, most of those code smells are really only code smells in application development. Most scientific programming code only ever runs once, so most of the axioms of software engineering are inapplicable or a distraction from the business at hand.

Scientists, not programmers, should be the ones spear-heading the development of standards and rules of thumb.

Still, there are real problematic practices that an emphasis on sharing scientific code would discourage. One classic one is the use of a single script that you edit each time you want to re-parameterize a model. Unless you copy the script into the output, you lose the informational channel between your code and its output. This can have real consequences. Several years ago I started up a project with a collaborator to follow up on their unpublished results from a year prior. Our first task was to take that data and reproduce the results they obtained before, because the person no longer had access to the exact copy of the script that they ran. We eventually determined that the original result was due to a software error (which we eventually identified). My colleague took it well, but the motivation to continue the project was much diminished.
IssueN17 Laws of UX-Brutalist One-Type Scale Generator – Device.CSS -Spectre.CSS
Google Cloud to invest $100 million in Amwell
Newly discovered MySQL bug: HAVING clause is not applied to all rows
> Intel literally makes custom processors specifically for AWS

Sort of. It's the same mask for everyone with the per customer special features either fused off, or just requiring a special MSR knock sequence.
When one post is on HN's front page it's common for there to be a rush of follow-up posts. Usually we downweight these since there's a power-law dropoff in how interesting they are. Some of the moderation principles relating to this:

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...

https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...

https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...

https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...

I'm wondering which of these S-1s are particularly interesting to discuss in their own right, vs. which are just follow-up/copycat-style threads? Unity is getting a specific discussion (https://news.ycombinator.com/item?id=24261559) but the other ones seem pretty generic. Oh yeah, that's another relevant principle: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor....
Asana lost 120m last year

Snowflake lost 350m last year

Unity lost 160m last year

Sumo Logic lost 43m last year

Jfrog lost 400k last year

Out of curiosity, is it normal for companies to IPO this far away from profitability, or is this a recent tech thing? I feel like it was a big deal when uber IPO'd so far away from profitability, now it seems standard.
> it would have the ability to directly hinder the businesses

They have extensive contracts in place. It's not like ARM instruction set is provided to nVidia and then they can just revoke it because they don't like nVidia.
Record high market, so why not?
I think there's something to be said for being a specialized generalist.

Being a true jack of all trades can mean you're mediocre at everything, it's better IMO to specialize on certain skills within different fields - ideally ones that synergize.
Every good system need to strive to be a meritocracy, anyone arguing anything else is just talking nonsense. If it is impossible to determine who has more merit then every system is doomed to fail.
People don't realize that antitrust did not originally apply only to the largest few companies in a market. Sure, it was used to break up Standard Oil and Ma Bell, notorious monopolies that openly used their monopoly powers to charge sky-high prices. But it was also used against companies large and small that were engaging in practices judged "anti-competitive". E.g., "Brown Shoe Co. v. United States (1962) invalidated a merger between two shoe producers and retailers because it would have created a market share of 5 percent that might have tended to “lessen competition substantially in the retail sale of men’s, women’s and children’s shoes in the overwhelming majority” of the relevant markets." 5%! Pretty amazing that a few retailers now control a huge percentage of all retail sales. To be fair, Amazon and Wal-Mart have mostly grown organically, but still.

https://www.hbs.edu/faculty/Publication%20Files/19-110_e2144...
So R&D is not a thing, but A&D is? That would be new to me