skysight-inc/HackerNews huggingface dataset:
So I just remembered, "I still do not have any news sources from Japan, which must have important journalistic activity - let us check again the Asahi Shimbun, and see if it has RSS".

The submitted article is the one that greeted me in the Asahi Shimbun frontpage.
I watched this video when it first came out (if you're not following Grady both his channel and recent book are excellent) and I think this part was particularly well put:

> That’s the nature of SpaceX and why many find them so exciting. Unlike NASA that spends years in planning and engineering, SpaceX uses rapid development cycles and full-scale tests to work toward their eventual goals. They push their hardware to the limit to learn as much as possible, and we get to follow along. They’re betting it will pay off to develop fast instead of carefully.

> But this wasn’t just a test of the hardware. It was also a test of federal regulations and the good graces of the people who live, work, play, and care about the Boca Chica area. And, SpaceX definitely pushed those limits as well with their first orbital test.
Great thread, bookmarked this one! I started programming over 10 years ago so I could make my own circus equipment.

I mainly blog about my IOT LED projects but there is a lot of creative coding as well which might be interesting to some.

Actually hit the front page of HN once with a post about how Ubuntu Snap update spoiled my world cup final (that ddosed my site with HN visitors, site was down for 2 days)

https://www.circusscientist.com/blog/
That means it is more like federated control IMO.
What is it that has managed to convince you that Russian leadership is suicidal?
The alternative is the SLS, how many billions down the drain is that?

The true issue with the launch was the flight termination system taking 15-30s to trigger, which they have had to requalify since that is what protects the public from harm.
Identify your target audience: In your case, it would be restaurant owners who struggle with keeping their menus up to date on delivery apps and online platforms.

Define your research objectives: Determine what specific information you want to gather through your market research. For example, you may want to understand the challenges restaurant owners face in updating their menus or their willingness to adopt a new solution.

Conduct competitor analysis: Research existing products or services that aim to solve similar problems for restaurant owners. Analyze their features, pricing, customer reviews, and overall market share.

Gather feedback from potential customers: Reach out to restaurant owners through surveys, interviews, or focus groups to gather insights about their pain points, needs, and preferences related to menu updates and online platforms.

Test your product concept: Create a prototype or mockup of your product idea and present it to potential customers for feedback. This will help you validate whether your solution meets their needs and if there is sufficient demand for it.

Analyze the data: Once you have collected data from your market research activities, analyze it to identify patterns, trends, and key insights that can guide the development of your product.

Refine your product strategy: Based on the findings from your market research, refine your product strategy by incorporating customer feedback and addressing any identified gaps or opportunities.

Remember that market research is an ongoing process that should continue throughout the development and launch of your product. Stay open-minded and adaptable as you gather insights from potential customers and make adjustments accordingly.

Good luck with your market research journey!
The problem with this argument, when talking about space, is that precedent is often so extremely conservative and over-engineered that there's likely to be a huge middle ground between "good enough" and what NASA did in the 60s.

NASA built a launch pad with a flame diverter and water quenching system - and it worked! But now they have it, they're unlikely to test launches without it. Space X clearly think that there's a middle ground - something which is simpler, quicker and cheaper than the status quo, but which is good enough.

Clearly they failed - and arguably they were irresponsible not to do more tests. Given the environmental repercussions of failing, they probably should have started with something closer to precedent and worked iteratively to simplify it. But when you're talking about this sort of very low volume system (how many launch pads, total, are there in the world?), precedent is only worth so much. (It's also the reason so little progress was made in re-usable launchers until SpaceX came along).

Hardware is not software - I completely agree. But you can only make progress by testing hardware. Assumptions are rarely correct.
> But given forward warning, it is possible to shut off or limit the energy flow prior to the event - it will mean voluntary blackouts for a few hours but it is better than a forced blackout for a few months.

The last few years have shown that leadership in certain areas has Cluster B personality traits, and will do the opposite of good advice just because it feels good to be contrarian.
>If you remove the ads, suddenly, it evens the playing field. They have to compete with the product, not the brand.

Well, you at least levelled one of the playing fields (while also removing a huge eyesore, which I really like!). I think the business deals in the background play a very large role too, if not bigger than the advertisements themselves. By business deals I mean that many restaurants exclusively serve the coke or pepsi family of drinks. This won't change if we remove the ads, only strengthen, and the larger players have a bigger weight, so the field is still very tilted.

That plenty of businesses would die without ads, I completely agree. There's an entire business model of running a bunch of ads, selling a bunch of crap, then disappearing. I would say good riddance to these.
This is a very astute way to look at it. I'd say then that the value of Slack is to be user friendly, which suc definitely is not for muggles.

But then more difficult questions arise:
- Is the price of slack worth it, when the alternative is having more educated users that can do very basic command line calls ?
- Same question, but taking into account that Slack captures your data and won't give it back to you ? How expensive is it to leave Slack ?

Sure, suc sucks, but we probably could converge on something less bloated and proprietary than Slack ?
Eh, I read this a lot. An app architecture is not a framework, frameworks get complicated because they have to be generalised enough to serve multiple projects with different requirements which leads to a ton of abstraction. Then because they're complicated they're difficult to learn.

An architecture concept just needs a page or two of docs and diagrams to understand, and the code is right there in the app. You don't need a framework to implement relevant design patterns.

Those apps can also last longer, because there's less pressure to rewrite in React/Svelte/Solid/etc when the existing code isn't dependent on some obsolete framework - Ember/Angular 1/etc.
https://peterhung.org - Mostly on life lessons - though I'm dev by training.
English-only list of posts: https://peterhung.org/tag/english-articles/

My favorite is a post written more than 10 years ago on Buddhism: https://peterhung.org/lessons/you-and-i-the-3-levels-of-conn...
That's not "recency bias". Rather than "recency bias", I suspect you meant that data from the past is less accurate and less complete, due to measurement technology, measurement techniques and record-keeping.
Dimmable LEDs do dim. And good LEDs don't flicker.

LEDs run on DC, so connected to AC power they need to turn that into DC. If you do that without a capacitor to smooth things out, you get flicker, which may be the case in cheap LEDs, but good LEDs will have a capacitor and therefore not flicker.

A LED lamp consists of many individual LEDs. Dimming a LED lamp involves turning off some of those individual LEDs, rather than supplying less power to each of them. A LED lamp needs to explicitly support that or it won't work. But those LED lamps exist. Similarly, LEDs that only produce dim light for situations where you only want dim light, exist.
as someone interested in BBS that has next the no experience with (and barely any knowledge of) any of this, would this be a good starting point to start exploring?
I’m out of tweets for today. Can someone post a screencap?
Totally agree. I think where complexity really creeps in is as you add multiple new content editors with varying skill sets.

If you want a team of people that don't know HTML or rest of the stack to edit, manage and deploy it then you're going to need a more complex abstraction.

The alternative might be a training programme for new staff in HTML, CSS, git and rsync.

You're trading one type of complexity for another. As you say, it all comes down to use cases.
Wow, I noted it looked strange and spotted some things other people mentioned, but somehow completely missed the windows... I'm sure there is some sort of name for this thing of not spotting the obvious while getting the details.
> Why is the Steam Deck Linux based while Android hardly has any decent games?

This is entirely a market issue; you can port Unity games provided you can adapt to the weaker GPU, but you have to deal with the small screen and touch controls. Plus people have got used to everything being free on Android, so the really big money makers left have to be gatcha-monetized.

> On Android you don't need all kinds of containerization nonsense with 100MB packages for even the tiniest things.

Have you looked at some Android package sizes lately? They all bundle their dependencies.
That's not a gotcha on Proxmox projects but a gotcha everywhere, SWAP on ZFS needs a lot of special care to avoid that it needs to allocate memory during swapping memory out (e.g., if low on memory), causing hard-freezes.

It can be made somewhat[0] stable with using no (or a simple compression like ZLE), avoiding log devices and caches it can work, but it's way simpler and guaranteed stable to just use a separate partition.

[0] even setting the myriad of options there still exist reports about hangs, like https://github.com/openzfs/zfs/issues/7734#issuecomment-4167...
Wonder if Musk is then as safety, and build conscientious as Toyota, the "it must have been car mats!" throttle company.

But, some just love to trash Musk.
It's interesting to think about where such a principle would land.

I think having five lines of code (well, it's more like 50 of so reading the article) with some key and reliable dependencies is better for maintainability than having no dependencies but a substantially larger code base. As you point out, there's definitely limits, and npm's left pad, is odd and is even packages are obvious example where the added dependency is less maintainable than implementing the code directly.
I have a substation in my back yard, approximately 15ft from my house.

Anyone have a sense of what "damage to transformers" means? Like, it frazzles out in its own housing, or takes half my street out?
Boosted Tree Predictions in SQL
Deathstar only needs skeleton crew to run.
Implementing full-duplex protocols asynchronously is much simpler.
> Ships will sail around the world but the Flat Earth Society will flourish. There will continue to be wide discrepancies between price and value in the marketplace, and those who read their Graham & Dodd will continue to prosper.

https://business.columbia.edu/cgi-finance/chazen-global-insi...
When I think of hobby projects to have over my summer vacation, I'll make sure to get back to this list! All of these really trigger my curiosity.
You should check the app sizes on Android - I've got very few under 100MB and that's exactly because they ship all the needed dependencies with them. That's how you avoid the issues during upgrades both on the phones and servers.

The phone apps don't use the exact same system for it, but essentially they're fully isolated in a similar way containers would be. The only difference is what is provided by the system and what by the app.

Flatpak can also shift the GUI into the base layer, so for example on Fedora Silverlight you can have a barebones system which uses a shared gui layer for most installed apps. (CoreOS is a similar idea, but for the server side)

> It's not hard to imagine extending that model to cover things like databases

Databases are not interchangeable beyond trivial examples. But a plugin system like that exists - odbc.

> when the app can just say "Hey, I need to make a database, I can use ...

This can be already solved with either full system configuration (Nixos) or containers (docker-compose does pretty much that). Those are sane and structured as well and they're available now.

If you want to go one layer higher (lower?), you can build a similar environment with AWS cloudformation - they can provide you with app containers or isolated functions, ready databases, all the connections in between.

> Apps use things far slower than Dart and Kotlin and Android API calls all the time.

Yes, but on the phone your app may just take slightly longer. On the server side a common case taking longer means everyone else waiting a bit longer and the whole thing translates to more money spent on infra. Those are different failure cases / requirements.

> Why are we not managing our web apps by uploading a single APK file and a settings.ini with the permissions we want to give it?

Many of us are doing basically that. The APKs are container images / static binaries / other kind of packages though. My whole server is one Nixos configuration file for many services and packages for example. Some older systems won't change overnight, but for new stuff you have all the possibilities you want, available right now.

Probably the closest to "just put some blocks together" you can get now are the iot fleet management services OSes like balena and others.
> then I think you are not a good coder and you should learn more instead of worrying about that

I am not sure if its that simple and/or so black and white. Everyone is bad when they start, and even stay okay for a while. So fear is very rational, the fear of getting replaced by someone or something better is very humble. No matter how good or bad one is, theres always someone better than them.

I think for most people its smart to adapt to using AI in their workflows to make them better and more efficient, so I think everyone benefits from learning no matter what skill level they are on.
Ey, here's my blog => https://0xbro.red :)

I blog (and make videos) about what surrounds AppSec, ethical hacking, penetration testing, CTFs, and other various cybersecurity stuff. I also plan to do vulnerability research and responsible disclosures in the future, but only time will tell.

You are welcome to my web space!
I suspect the thing people find offensive is that this is not the default
The alternative with threads on an IO-bound server eventually cycles back to async/await but with extra steps. You write synchronous request handlers until you notice IO-waits wasting all your thread time, add more threads to the pool, start hitting overhead from that, then implement greenthreads.

NodeJS did it right, and it's hard to call a 14-year-old technology a fad.
OP is talking about having a mechanism / Operating system for servers to easily deploy and manage. Atleast, that's what I understood from the original post. How does k8s help me deploy say a blog ? It's just too technical and geeky. If this was "Android", I just download some blog app, click and install. Don't have to worry about updates either.
> replace urls on YouTube content to show lower resolution copies of videos.

Tell that to mobile providers who can downscale my twitch and youtube videos and require premium to have higher resolution...
What I've heard (and what basically makes sense to me) is that falling back to the network layer as an abstraction is borne of web programmers trying their hand at building native applications (they do not know what dynamic linking is), with all that comes of it (both positive and negative).
Jesus claimed to offer everlasting life to those who believe in him (see Gospel of John). Worth looking into?
I don't think it's a stretch if you're accusing a member DoD of having blood on their hands to assume that the intent of that statement is that the blood is there due to unjust actions and, since the DoD primarily kills people through war like activities, that the blood that was on their hands was from some sort of unlawful, war like activity, aka, war crimes.
Who said innovative? I just said that the problem that uber was trying to solve was a known problem.

Also btw legal shenanigans could be quite innovative. Word policing like this doesn't achieve anything.
Easy, just block them at night
But technically Goland isn't 'on a subscription model' but a 'you want updates you need to pay for it model' , nothing stops you for just paying 1 year and having that license for life :)
Looks like she ended up very proud of her authentic self, thanks to VMware.
>Not specific to rust, but I think asynchronous programming in general is a hype.

Hmm, wasn't the whole point of doing things in event loop because it way out perform thread-based architecture? Like when Nginx way out performs Apache? On a single core CPU of course.

Edit: It is not that event-loop is better than thread-based, just in a web server scenario it just perform much better.
And I'm hoping to ship my product in a month, even though we've already put in half a year and have loosely connected backend, frontend, servers and clients, most of which are barely a prototype.
A decent appartment building will allow you to do all of that as well.
I'm very puzzled by the lack of Android desktops. Most users (not high-end users) would rather use the same OS and apps on all their devices, and Android is perfectly OK for content consumption, Office-type work, social and comms, light games...

There were a few very early attempts at Android laptops, but as for tablets (only worse), w/o any support from Google (Playstore category, guidelines...) those floundered.

I blame mostly ChromeOS, preferred by Google because it fixed the NIH issue and because why build one good ecosystem when you can build an OK one AND a bad one ? I'm still making "Android desktops" from TV boxes for the elderly around me. Android's support for standard webcams and other USB devices is a boon. It only really needs an LTS version, and some devices/apps guidelines and vetting. Not sexy enough for Googleheads, I guess ?
Most people on here (generalisation) spend more time on a computer than in nature. If you spend time in Nature it is very obvious what is happening. Look at the world from whence it came and where it is going.

Heating of our climate is but one thing.
> Only if you know that foo is an async function. You can't tell by the function call itelf.

That's fair point, but traditionally you don't use blocking functions in async contexts at all. It is fairly easy to lint for by prohibiting some inherently blocking calls eg.g std::io, although they might sneak in through some third-party dependency.

This doesn't have an easy solution because Rust is a general purpose language that allows different styles of concurrency adapted best to the situation, instead of one-size-fits-all like Golang.

Rust has means to annotate functions so maybe there will be some automation to deal with that in the future, similar to how `#[must_use]` works now. E.g. `#[blocking]` or whatever.

> I'll have to check the compiler settings.

This is with default compiler settings.

> Why couldn't the compiler clearly state the reason for the error though?

Stating the reason is probably solvable problem, but there is another problem: what if 5 layers down the call chain something suddenly introduces a potentially blocking (awaiting) operation? This would mean that some code that previously compiled now has to stop compiling even though it hasn't changed and even though none of the signatures it uses changed. I guess it would break things like separate compilation.

And again, it would be less readable than it is now. Now it is fairly simple - you don't have to look down the call chain to know that something can do await.
The ability to invest is a privilege, since most of us cannot afford to do nothing but learn and wait until a good investment opportunity shows up.
ourworldindata has some neat graphs for this. Even though they cover only small slice of history and geography, its still provides some insight how longevity has evolved: https://ourworldindata.org/life-expectancy#it-is-not-only-ab...
They were bombing their own nuclear power plant!
That combined with Patreon does! I'm likely going to spin up a small corporation so that I can funnel my side income through there and avoid having to go through the logistical nightmare of double income tax because of imperialist IRS policies. Sometimes I justify fun purchases that I could afford anyways (eg: very used camera lens or that Anbernic Win600 that I ended up liking for 2D games but couldn't hold comfortably enough to use the sticks) with ad/Patreon income. Sometimes it ends up on the blog anyways. Stay tuned!
"It is not a she, it is an it" - Mrs Davis (talking about Simone)
https://apnews.com/article/tesla-china-recall-accelerator-pe...
The actual percentage is higher. Steam has a lot of games they mark as unplayable that are very much playable with only a few tweaks, but since they don't just work right when you press play they say it's unplayable.

ProtonDB is better, though it does move slowly. Basically if protonDB says it isn't borked, the game will run.
We might pretend that we have no interest in women*, but it's just that after you get old enough the machinery just doesn't work as well and we don't want to majorly disappoint our new partners when we don't perform properly.

we're interested! We're still very* interested!
Yes something like that happened in this dusty, old machine. Good thing she was using the PC when it happened and unplugged it when she smelled the burnt plastic.
It isn't data science. It is earth science.
As a very frequent nagger about the lack of type system of Elixir, this made my day:

> The type system will extract type information from patterns and guards to find the most obvious mistakes, such as typos in field names or type mismatches from attempting to add an integer to a string, without introducing any user-facing changes to the language.

> By propagating types from structs and their fields throughout the program, we will increase the type system’s ability to find errors while further straining our type system implementation.

Congrats to them.

I still wish it had been implemented 10 years ago, but, hey, that train has sailed a long while ago. (I know, trains dont sail. Or, as we say in Elixir-land, "** (MatchError) ...")
Yes they know the problem, we for sure know Elon himself did know the problem, they went ahead with it anyway. They don't care if they damage some wetlands or create large dust clouds or similar, they simply write it off as a fine which they expect to not affect them in a major way.
Large FOSS projects are social movements, because they have to attract contributors somehow, and they reflect the wider culture. I read modern GNOME as a symptom of longue duree (historiographical term, meaning something that exists for a long time in the unspoken background) of Jobesian thinking that people caught as users and designers.

There might be all sorts of economic justifications for mainstream proprietary tech doing this, but for a well-funded FOSS project it has to had become a cultural thing.