skysight-inc/HackerNews huggingface dataset:
The “lecturing experience” for most lecture-exam format STEM courses is sitting on your tuchus/tuckus and watching the lecturer. How can that be made more meaningfully immersive than just sitting in a more comfortable chair and watching a video or streaming, which is proven tech? The occasional relevant question is usually more an annoying delay for the entire class than insightful, if the lecturer is at all competent.

Socratic method, dissections, labs with simulated better-than-cutting-edge equipment…maybe there’s some opportunities. The issue is this is second/third generation technology development/refinement (20+ years old from an R&D standpoint) and doesn’t have the sizzle of brand new stuff. It’s more of a slog than a sizzle.

Enhancements like sidebar information providing remedial-related material or AI-driven answers to typed questions, combined with video pausing might be pedagogical improvements but that’s hardly more immersive. Perhaps just better, but available with 10 year old tech. The technology may be outstripping the pedagogy…
Some projects _never_ make breaking changes, and major version bumps represent major additions.
I’ve definitely spent a ton of time on dependency work. I think the web app ecosystem is unique compared to its counterparts because the platform is really not designed for applications; it’s designed to render documents. You get so much more out of the box when developing for proper application platforms like iOS. For example, dealing with dates and internationalization. iOS gives you enough tools to not really need an extra library. Not so with the web.

Plus, the std for these platforms is much larger too, because you get access to the huge API surface the platform provides. Apple has spent a significant amount of resources making the platform decent to develop for. They even include reactive UI patterns out of the box now; something you’ll need a library for on web.

I think that’s the real shame. The web platform is very flexible and ubiquitous, so most people try to target it. But in doing so, you’ll need to account for web standards differences across browsers (using a tool like browserslist), the cost of downloading the source code when navigating into a page (with webpack and minification to make bundle sizes more reasonable or split up), and the cost of not having strong default patterns for stateful, interactive UI.

Every other platform will include nearly all of the tools you need within the IDE and on the platform. Web just doesn’t have that, unfortunately, and it has further problems that really don’t exist on other platforms. (For example, other platforms don’t rely on downloading the app source code from a remote server when launching it every time.) It relies on the open source community to provide solutions to so many problems, resulting in the complex dependency trees we see in large apps.

On the one hand, the OSS spirit is admirable. There are competing projects for nearly everything, similar to Linux programs. (Just like there are many Linux dependency managers, there are multiple JS dependency managers.) This allows projects to “get better” by competing with each other, but at the cost of breaking changes and maintenance over time. (For example, there are many projects aiming to provide the fastest JS bundler.) But there is something to be said for having an opinionated platform with more features like iOS or UWP for windows.

All that to say, I don’t think this is a JS shortcoming, but a shortcoming of the web platform in general. And some of those shortcomings are inherent to the benefits of the platform.
I wish Congress or say corporate boards would do the same.
Took a year of attempting bipolar treatments before my doctor finally agreed with ADHD diagnosis at 25. I’m glad she stuck with it but it sounds like I wouldn’t have as much luck even getting help now.
I find it amazing that Ireland would be eating a plant from the west coast of an isolated mountainous region of South America less than 100 years after Europeans went there. Even things like oranges and bananas were rare in the late 1800s early 1900s in the US and Canada.

It's amazing how much of food from the Americas mostly central and southern is normal everyday food. What would we all be eating if the Americas went undiscovered until recently?
I work on a dependency-free, build-less library called htmx:

https://htmx.org

It's more an extension of HTML than a JS library. It might be a good way to gently introduce more dynamic behavior without blowing out the complexity of your projects.
rise in popularity of FIRE lifestyle with everyone in their late 20s too
I use my family account for other uses too.

I have a separate account just for Amazon Echo because I don't want my kid's selections to influence my main account suggestions.

I also have my own account for the car, where explicit songs are disallowed. This allows me to listen to the music I like, but it avoid explicit songs for when my kids are in the car and that setting doesn't affect my main account.
A sizeable minority is something that is still visible on a pie chart.
It's probably that and it's great marketing TBH. They could have just posted them on their own site or another palace that allows NSFW images (Reddit, Twitter, etc). But they probably also knew that a story about an art museum opening an OnlyFans is going to be fantastic marketing.
The problem is that the UMC status signalling game is heavily correlated with success in the real world.

Especially in law, where the status signalling game is a prerequisite in a very serious sense for doing the job, attracting wealthy clients.

If you hire someone from a working class background you basically need to teach them that on the job. Even in engineering it happens.
Sounds like a solid/healthy strategy to me.

With ignoring package managers, do you mean that you instead of running "npm/yarn install/add <package>" you inspect said package (which does what you need) and cherry-pick the functionality into your own codebase (or just outright copy it if its functionality is elementary to you), or that you try to write/reimplement it yourself?
It could just be "reveal answers".
The main issue is nobody is thinking for themselves, nor are they thinking critically about their call stacks...
I stick to pretty minimal dependencies (and more recently, simple build systems like esbuild or parcel) and I don't have a terrible time maintaining things over the years. But I can sympathize (to a point) with folks who haven't learned this lesson.

The more packages you bring in the harder it will be for you to upgrade (anything).

You have to learn over time what you must have implemented in a third party library and what would be better for you to maintain yourself.

I do wish there were a public grading system for JavaScript libraries that failed them if they bring in X dependencies or have low tests coverage. Any automated way that publicly guided/shamed library developers toward fewer dependencies would be welcome.
I agree and have quit Javascript completely. The ecosystem just feeds on layers and layers of abstractions. It seems the mantra is complex is better than simple in JS land.

Been developing with an HTMX/Django stack[0], and it has been a wonderful experience so far!

https://htmx-django.com
First, the primary use case of rockets (especially SpaceX) is satellite lift and ultimately Moon and Mars landing, not "wealthy tourists." Obviously the recent Inspiration4 launch shows that there will be tourist flights, but this appears to be the exception and not the norm (unlike Blue Origin and Virgin Galactic).

Second, there are approximately 100,000 airline flights per day worldwide; American Airlines alone flies 5,000 per day. Even 1,000 rocket launches per year would be equivalent to 5 days of traditional flights.

People disagree with the climate concern not because "Elon Musk is involved" - it is because critics are focused on the wrong thing. There are far more climate destructive practices with far less benefit to the good of mankind. All those 100,000 flights per day? That only accounts for about 2% of carbon emissions. A SpaceX launch, to use your figures, accounts for 0.00005%.

So why focus on this extraordinarily tiny fraction of climate impact? Is it because it's Elon? Because rockets look big and thus wasteful?

What about the incredibly important climate monitoring satellites they'll lift, or benefits like GPS, global internet, potential breakthroughs in space manufacturing, astronomy, or physics? Or even just the hope and excitement about the future that many feel in the face of otherwise depressing news everywhere. The massive size and lift capacity of the Starship (100 tons to orbit, 8m wide by 20m high or so) will transform activities in low earth orbit and beyond.

And I'll close by saying, yes I think Elon has earned a little slack - he has done more than most people on the planet to reduce global emissions. Tesla, Solar City (now Tesla solar), battery technology (which has been a massive impediment to clean energy storage), future electric long-haul trucks, and the supercharger network (to make extended travel on electric vehicles possible) all have reduced emissions tremendously - probably far more than the additional carbon from rocket launches (though I haven't done the math).

So that's my $0.02, anyway.
What sort of monetization do you imagine? From my perspective, ads probably won’t work well because it would ruin the premium feel of the platform. Shady paid-for influences (such as making something appear up high in some listing without being labeled as an ad) might work, but if they’re caught the user base would not be happy.
I don't buy this. The whole thing is enabled by hard work of browser developers enabling all this hot mess without much performance impact. JS is blazing fast and it creates a massive wild-wild-west of framework gold rush. Instead of being responsible, they create ever more bloatware that doesn't stand for 6 months.
One past thread:

Corretto – No-cost, multiplatform, developer-preview distribution of OpenJDK - https://news.ycombinator.com/item?id=18449506 - Nov 2018 (143 comments)
The idea that professional software developers will have their negotiating power depleted is preposterous.

Barring an AGI that can take care of knowledge work, companies will continue to pay a premium to developers because they are often times the core value creators of the business. Even in traditional areas like finance, quants with CS PhDs are displacing Harvard MBA’s trading on fundamentals b/c their returns blow the latter out the water.
Because then you cannot differentiate anymore between "NullPointerException as a bug" or "NullPointerException as a feature".

E.g. you might want to return the streetnumber of a user's address. When a NPE is thrown, was it because there is a bug somewhere in the code or because the user's address has no street number?

With Optional, it is clear: there was no street number.
I would love to consider retirement, but it turns out that our currency is worthless if it can't buy the things we need and want
The JS Ecosystem + The AWS / Serverless ecosystem is a love story of the likes of Harley Quinn and the Joker.

This week I picked up a gig working on a website for a non-profit organization, the needed some basic changes to a few forms. The reason they had to hire me, a web app developer, the site was built by some agency with Next.js / Jam Stack technologies, Contenful, AWS Lambda, AWS Amplify etc.

This simple website, is one of the most complicated monstrosities I've ever worked with. Every page downloads multiple megabytes of JSON from the Contentful API just to render dead simple pages with text and images. Every time there's a change in contenful, a new build in AWS Amplify is triggered to generate the site to static content... only the React code is so complicated with so many round-trip, nested server requests (n+1+1+1 etc) that the builds fail constantly because the API server (on lambda of course) which serves the Contentful content basically gets DOSed. I had to write logic to retry all app API requests just to get the builds to consistently work so I could work on the website. The code that transforms these megabytes of JSON into webpages must have been written by a mad man.

Also screw AWS for not building proper tools to debug AWS Lambda. Not having to manage servers sounds awesome, so everyone has started using lambda, but the developer experience of having to wait 10 - 15 minutes just to add a console.log line is like pulling out your own finger nails and then scraping them on a chalkboard. Then AWS built the most noisy, difficult to use and hard to navigate log management solution on the planet (CloudWatch), and started sipping their beers.

You can avoid these technologies all you want, but one day you're going to have to work with a project that choose to use them, and you can't control that. I believe library authors and service providers have a responsibility to think about developer experience that's being ignored. Or perhaps, since developers don't always have a choice in the technologies they use, building easy to use developer tools isn't worth it.
I think the decision to put it up on OF was pretty deliberate. A story about a museum opening an OnlyFans account is going to get alot more people talking than if the museum did it with the Fediverse or some other implementation.
Anyone have better photos, maybe from the 70s onward?
I almost fully agree with you, but a small part of me wonders if this is different, and we've created a sort of aristocracy that exists outside of normal competition and the rise and fall of companies. In some measure, it's going to depend on modernization of monopoly regulations. But I think there is an outside chance that were due for 50+ years of stagnation and increasing inequality, after the sort of cambrian explosion of tech we've seen since the 70s
Analogue video (e.g. television) interlacing did actually begin in the 1930s, a few years before the Hindenburg disaster. But the original disaster footage would have been shot on film (not interlaced of course), cut into newsreels and then converted to a television signal via telecine.

Supposedly the original newsreals still exist, preserved by the National Film Registry: https://en.wikipedia.org/wiki/Hindenburg_disaster_newsreel_f...
Rising living costs due to inflation and a few other reasons (such as global supply chains being a mess), will force workers into a scenario where they have no other reasonable choice but to strike as a bargaining tactic (if they can), as the companies aren't going to often voluntarily outpace inflation (ie inflation adjustment + normal yearly raises). The John Deere offer to labor for example was very mediocre. Deere can do a lot better, they're doing quite well right now, their operating income has climbed from $2.7b in 2017 to $7b in the last four quarters (and heading toward $9b). That kind of stinginess toward your unionized workers while the company is prospering will get you a strike.

Societal turmoil (worker, consumer, business) is one of the many not fun consequences from higher rates of inflation.
TypeScript's the first thing that's made JS tolerable, if I have to touch or use anyone else's JS code. It's pure misery, otherwise.

Writing solo and using no libraries, plain JS is... OK. Anything else, TS is the only thing that keeps me from hating life the whole time I'm working in JS.

FWIW I'm a huge curmudgeon who's usually (eventually) proven right when I hate some new thing that everyone else seems to think is great. TypeScript is wonderful.
This reads more like an issue with Vue (social, not technical) than a valid criticism of the JS ecosystem.

Vue.js is a great project for front-end enthusiasts, but if you look at business objectives (aka getting things done) you would want to use React for any web app: The ecosystem in terms of libraries, help articles, developers is at least 10x bigger.

The release of Vue 3 definitely makes this situation worse for a couple of years in which using Vue 2 is still an option. Effectively fragmenting the Vue-camp further.

TLDR: Use React with vite and pin your dependencies to avoid everything mentioned in the article.
Stuffing Ourselves – Amazon, the Postal Service, and the Tyranny of Logistics
The strike was averted with a last minute deal as of a few hours ago.
I have recently come back into web development after a long hiatus and this article really touches on a lot of issues I have had with JS development and trying to learn new tools and libraries. I really feel what that author is saying.

All of these cli tools that people use make me think of that boiling frog metaphor.
That was TripleByte's whole idea. They recently pivoted though :(
There are 3 artists that Spotify continually play to me and I preemptively will fast forward them even during the crossover play because I dislike them so much. I’ve submitted requests before to have a “don’t play me this artist” feature. I don’t know why this is so hard for them.
OK, so what is your estimate of net worth for a software engineer retiring today after 30 years in the industry?
It's pretty much a solved problem. Just use a language that has better ergonomics for errors.

Scala's ZIO is one of the better examples if you are interested to look into an alternative.
By looking only at share of wealth, this is missing the fact that total wealth in the US has grown tremendously over the time period in question. In absolute terms, the inflation-adjusted amount of wealth held by the Baby Boomer and Millennial generations at similar ages is about the same.

In 1989 (the first year in the Fed's data), the Baby Boomer generation held $4.33T in wealth, which would be $9.5T in today's dollars, while in 2021, the Millennial generation held $7.47T in wealth [1]. While that's a little bit less, it's important to keep in mind that the median age of the Baby Boomer generation was 34 in 1989, vs 32 for the Millennial generation in 2021. If you linearly extrapolate Millennial wealth growth, the generation would hold $10.5T in wealth at a similar age.

So what the linked chart really reflects is that the total size of the pie has gotten much larger in the past 30 years. Most of the increase has gone to older generations, but I think that's neither surprising nor undesirable -- after all, 30 years ago, the Millennial generation ranged from not being born yet to elementary school. Will the pie continue to grow over the next 30 years so that Millennials can see a similar increase in wealth (and hear complaints from the kids being born right now)? I'd imagine that's largely up to the decisions we make today.

[1] https://www.federalreserve.gov/releases/z1/dataviz/dfa/distr...
They don't have a family tree... They have a family ladder. Wow.
you can also boot netboot.xyz.iso from ventoy without configuring the network :)
Is it time for baseball to adopt robot umpires?
Bread and pasta, perhaps?
What's a test going to tell you? The reason he's saying it's a bad idea is because it's possible to end up with the printer executing a partially submitted job or not using settings that match up with the document you're trying to print.
Depends on the status of the semiconductor factories being built outside of Taiwan.

The US only espouses human rights or morality grounds when it needs bodies and financing to engage in a conflict. If it doesn't need that then see what happens when you try to convince any of the other 200 countries to support you.
tl;dr blindly upgrading 100s of dependencies didn’t work out. But, is this instability due to the ecosystem, or the choices of the developer?

I work on a large, highly interactive web app that does a lot of the fancy stuff like code push to native apps, offline caching, heavy use of browser storage, real time collaboration. Our stack is React, Express, Typescript, built with Webpack. Every year or so we upgrade one of these major components, like Webpack, which does take a week, following a semver major migration guide, but usually nets us some performance and developer productivity wins. I’m sure if I tried to upgraded all our dependencies at once, it’d explode. So, we don’t do that.

Maybe I sound like a C developer arguing “C unsafety is fine, just don’t make mistakes”. There’s a ton of hype around JS libraries — of course there’s bigger hype waves in this ecosystem given its population and ease of publishing (compare to Java where you need to open a JIRA ticket to publish to maven central) but it’s a personal choice to follow fads like installing this ChakraUI thing or to use boring tools that you already know work.
Academic computer science uses many different models for analyzing computational complexity. Most of them are not taught at undergraduate level, because students generally expect to graduate without spending 10+ years at college. Computer science is a wide and diverse field, and it's impossible to teach everything every CS graduate should know in any reasonable time.

The random access model is usually taught first, because it works reasonably well in most situations. A slight variation of it, the cell-probe model, tends to be more useful for proving lower bounds. In that model, all computation is free and only memory accesses count.

A more practical variant of the cell-probe model is often called the external memory model. The computer is assumed to have M words of fast memory and an unlimited amount of slow memory that is accessed in blocks of B words. Computation is still free, and parameters M and B are both known to the algorithm. This model is useful in situations where accesses to one level of memory hierarchy dominate the running time.

The cache-oblivious model can be useful in situations where many levels of memory hierarchy matter. It can be understood as the external memory model with unknown values of M and B.

Another useful technique is parameterizing the complexity in terms of key operations. If operation X takes t_X time, we can then say than an algorithm takes O(|P| t_X log n) time with pattern P and problem size n.
This take only makes sense if you assume the next 40 years will be similar to the last 40.
I ditched javascript long ago for exactly this reason. Spaghetti dependencies everywhere you look.
Probably because Spotify takes payment from artists to play their songs. Promoting before a new album, etc.

If they let you block artists then this is less money for them.
I am with you. Don't be embarrassed. I spent a lot of time looking at Vue, React and the others and frankly I don't see how the time and effort are worth it unless you work in a large firm that has a lot of developers working on a large project.

I use npm and node because it allows me to write local tools that I write to help me manage data and convert it. I have a lot of other tools that I have access to but I can thankfully access it via CodeKit on my Mac so I don't have to waste time installing and learning them all.
People complaining about the colors shifting don't release it pulsated red in time to the phat beats it was dropping.
Based on some benchmarking details¹ for my application, it appears that Rust is willing to completely fill its hashmap. It may be that my use case is somewhat unusual in that I'm expecting most requests to not return a value,² but I found that just specifying a larger initial capacity dramatically sped up the application (I got a bigger speed boost from that than I did from switching from SipHash to FNV).

1. https://www.finl.xyz/2021/09/30/building-a-trie-in-rust-opti...

2. And since this won't be the only char-indexed map in the application, I will have to revisit this.
What are the others that you have tried?
whoa thanks for the heads-up! I've always wanted to try other platforms but I've thought it impossible since I have so much data in Spotify. Any gotchas here?