skysight-inc/HackerNews huggingface dataset:
But they also come at the expense of control. Once you pop the chute, you're a passenger, you no longer have the ability to control or point the airplane in any preferred direction.

If you've lost that ability already, the chute is fine, but if you still have the ability to influence your path, being able to pick what you hit and how fast you hit it can be worth a lot.
Mathematics is just a collection of cheap tricks and bad jokes - Lipman Bers
If you go to the google fonts version of this font ( https://fonts.google.com/specimen/Atkinson+Hyperlegible )

It DOES use SIL Open Font License. Maybe it's dual licensed?
Huh, looks like you're right. I distinctly remember getting an error for emoji domains but not normal ones. I might have made an incorrect assumption from that. Either way I've accepted I'm never getting that domain back.
Finally, a simple and correct way to render multi-colored text with Unicode ligatures. Hope Raph Linus picks this up soon. /s
I honestly can't say enough good stuff about the Kotlin Multiplatform system. You can use your React. You can bring MUI, so it's pretty by default, and animations / UI are really smooth.

Because of Kotlin Serialization, you can speak Protobuf or JSON really easily with Kotlin data classes, across platform boundaries.

Kotlin Coroutines support means your implementation code can work on top of ListenableFuture on the JVM or Promise in the browser.

It's just great. Very likely to be maintained, and even improved greatly, over the next 10 years, as it is the basis of Jetbrains' own business.
It's the same for California as well
I came across SAP in my finals at the University, it's such a huge company with great use cases.
My pleasure, it’s a bit of a hobby for me. I hope you manage to find your answers.
they are alternatives, not complementary. Unpoly seems to include more features, layers are particularly impressive.
I'm happy to pay for a decent junk filtering service that will work with hotmail, but I've yet to find one (I've tried a couple).

BTW most of the new spam messages come from a sender with the domain achildsplacelearning.com.
Not sure if this is indicative of anything much: https://www.abuseipdb.com/check/192.124.249.5
The issue with these articles, is, they assumed, bad architect divided wrong domains into "wrong microservices", then concluded, "microservice" is bad strategy.

Step 1: Understand the domain first.

Step 2: Use microservice for each domain.

If you failed at step 1, step 2 is wrong.

Monothlich architecture just "skips" step 1, and use one big fat service for all.
Sure, but apart from a rebuttal, it's also a valid critique to simply point out that this is a structurally bad article which insults the intelligence of the reader, without responding to the content. The entire field could be occupied by historians who only believe that class dynamics explain every phenomenon -- such that there's no contrary sources to provide -- and it still wouldn't make it an accurate or acceptable historical essay.

Here's merely one (of many) better articles that explains why people of San Francisco, than as now, might not favor having an openly lawless neighborhood in their city: https://theculturetrip.com/north-america/usa/california/arti...
You’re right. My mother, herself a career long LEO, taught me something very early on in life: violence is the ultimate authority in this world. I imagine she learned that from her job.
"Abstract: The Art of Design," a series that profiled a notable designer in each episode. It's a bit uneven, and some of the episodes spent too much playing up how clever and amazing the designer is instead of their work, but on the whole it provided an interesting glimpse into the design process in various fields. I particularly liked the typography episode with Jonathan Hoefler.
F for Fake by Orson Welles. Documentaries on art forgers (not 'how this art forger was caught!' which is of secondary importance) all tend to be interesting, but this is transcendent.

The Pervert's Guide to Ideology' by Slavoj zizek/Sophie Fiennes.

Hypernormalization* is an Adam Curtis doc so you'll love or hate it, but I think it's his best one.
Using DHCP to send a DNS search path can make this work across a lan, which is how it works in most work environments.

If you set your dns search path to example.com then http://go would resolve to go.example.com which could be your link shortner.
Relevant video from The 8-Bit Guy: https://www.youtube.com/watch?v=ZxQjMlwDA8A
Yes, I think so. What's the point?
Has Safe Return yet been used in an emergency? I've seen the demo videos, but haven't seen any news reports of it being used for real.

It's not wasted hardware even if not used. The aircraft already has a flight control system capable of flying from waypoint to waypoint and landing. Safe Return adds a layer of software able to compute and enter a course, while squawking Mayday and playing canned emergency messages on the guard frequency. New hardware is just a radio altimeter for use in landing, and the ability to lower the landing gear under computer control.
I recall seeing go link stickers around Google's Mountain View campus in the early 2010s! That was the first time I had seen something done like that, "overriding" an entire TLD zone (not that `.go` is in use, anyway) to serve custom content.

Do you happen to know how Google, or any other places, do this? I assume a custom DNS resolver being forced on clients through a network could do this, or maybe hosts files for each machine.
Fantastic series. Ruth Goodman is a national treasure, and Peter Ginn and Alex Langlands are also extremely watchable.

I'm personally partial to Victorian Farm, both because it's at a very interesting point in time — much of it pre-machinization, but also an age of scientific discoveries and agricultural improvements — and because I feel like it's the season where they are the most self-reliant (the farm they move into is disused and they have to renovate it) and living in the most realistically re-enacted environment.
This got a lot of on the internet, but I found it so incredibly boring.
I was alluding to the geo-libertarian position that the ”fair” distribution or ”land”(in the economical sense) is fully compatible with capitalism, and not necessarily communism.
> It then claims, without reference, that the VCR was a market replacement for physical sexual encounters. It goes on to ignore that AIDS was a health epidemic related to these sexual encounters, and that when the seedy operators are finally taken out of an area the real estate values increase.

I don't think you read the article very carefully. The sentence immediately after the mention of the VCR is about how AIDS led to the closing of many venues. The one after that is about the role of property values (though it claims causality in the other direction--that sex clubs were priced out as neighborhoods got richer).

> What value is this essay supposed to have to this particular forum?

Overall the essay reads to me as being very light on editorializing, and much more of a straight-ahead narration of an important facet of the city's history. I learned a lot from reading it, despite having lived in SF for many years.
Do non-technical professionals and SMBs need a simpler analytical tool?
The problem is, it's not one dependency. Several important libraries pull in a variety of wrappers and adapters - just to name three:

- glog (gRPC)

- logr (OpenTelemetry and friends)

- klog (Kubernetes client)

It's quite conceivable that even having decided to use zerolog, you end up with at least four separate logging libraries in your dependency tree before having written any of your own code.
Views, especially Materialized Views if you’re on Postgres, are about as close as you can come to a “one neat trick that solves all your problems” in modern software development imo.
This time there was a good reason for postponing the switch. Originally it would have been the same day of the constitutional referendum. It was a good call to remove one potential factor of chaos from that day.

Having to deal with online calendars being off by one hour for a week is not that bad in comparison, we are already used to that :)
I've been very excited to see Django embrace asyncio, and your package looks like a great way to do async task queues.

I've built a lot of very low traffic Django sites that are all behind user login for only a few users (think company internal-only CRUD tooling) and being able to use a task queue without having to set up a Redis thing is a big bonus for me.

Excited to see how this evolves, thank you for sharing it!
Yeah, those are kinda cool. They have the added advantage that they don't have a huge amount of bass, though what they do have is impressive for their size to be fair.

But because of their size they don't always activate room acoustics in a crazy way, and a lot of people monitor with them fairly close so don't need them loud either further lessening the problems.
Last week felt like I finally understand how webauthn and passkeys work - now my auth server has a "passwordless" login flow https://github.com/authcompanion/authcompanion2
You can use python with Electron ... with all that Electron implies.
^^^ Thank you! ^^^ Came here to reccommend Connections by James Burke and glad to see someone else has mentioned it. It's a masterpiece of popular science production made better with the grainy film patina of the 70s and 80s.

https://www.youtube.com/watch?v=XetplHcM7aQ
I've been trying to learn how to properly use Twitter to market my startup, and I found out that hashtags are better than cashtags when tweeting about stocks. That is, #AAPL is better than $AAPL.

This is the reverse of what I had expected because there seems to be vastly more people using cashtags but my theory is that 1) people still search for hashtags and 2) more volume means your tweet is visible for less time.

However, the best is obviously mixing them. I have a thread during premarket trading hours where I discuss stocks that the algorithm has decided is interesting and I'll print out the current score using hashtags, but use cashtags for quick discussion on stocks.

Example here: https://twitter.com/0xsmcn/status/1568155410191851521
I wrote definitions in the example, and the order dependence is clear.
I wouldn’t recommend renewing your domain every ten years, but I do always purchase my domains for ten years and subsequently renew every single year. That gives me a modicum of safety from certain life circumstances (e.g., there’s an HN commenter who lost access to his email due to a stint in prison).
> Audit logs are different from debug logs

Very much so - audit logs, where they are important, are often part of the actual business domain and should be explicitly modelled, not delegated to infrastructure with a slightly different level.
The problem with Cirrus is the parachute. Insurance companies don’t like it because instead of half or more of aircraft landing safely on a road or in a field, they are now all write offs.
This then adds insurance premiums. We are also now in the position of having to do extra annual training (irrespective of experience) to get insurance because so many amateur pilots are flying Cirrus (I think it’s the new V tail doctor killer, minus the killing). You have been warned: there are better aircraft out there imho.
And I haven’t even started on the flight controls (spring feedback is terrible), unstable yaw stability without yaw dampener (pax vomit profusely), and single power lever which decreases rpm with power resulting in an aircraft unable to (easily) slow down (without idle) which is normally done with prop braking. This results in energy problems similar to airlines where rookie pilots who cannot think ahead end up with too much energy. Also these modern long thin glider wing designs trying to get +5kts more can go to hell - they are getting so large it makes ground handling difficult; often longer than the airborne saving. If you want to get there faster, you save time on the ground.
A decked out RV-10 is a good alternative.
> It's similar to data engineers thinking they will do real ML some day and their data job is just temporary...

Hah yeah but this is just the reality of ML. "Engineer who only codes up awesome new ML algorithms" isn't a real job. For every 1 person coming up with exciting new algorithms, there's 500 people dealing with data pipelines, cleaning, maintenance, and operations. A while ago I got hired by a large SF tech company as a "machine learning engineer" and my team spent nearly all of their time writing Javascript web wrappers on top of scikitlearn. Thrilling stuff.
> This means valgrind cannot really detect memory issues as well since Odin has it’s own internal allocators. helgrind cannot work because Odin doesn’t use pthread primitives. ltrace cannot work because that just provides wrappers over every libc function, etc

Unfortunately, I've gone through too many bugs that had to be fixed through valgrind debugging that I'm unwilling to part with it
I just watched this while traveling in Croatia and Bosnia, and I thought it was an incredible documentary! It's also very interesting that it was made only 6 month after the Dayton Accords ended the war. It gives you a very in-the-moment view of events. Definitely worth checking out!
We have found out that, while some applications are installed much easier with Docker, operating them becomes much more harder on the long run.

NextCloud is a prime example. Adding some extensions (apps) on NextCloud becomes almost impossible when installed via Docker.

We have two teams with their own NextCloud installations. One is installed on bare metal, and other one is a Docker setup. The bare metal one is much easier to update, add apps, diagnose and operate in general. Docker installation needed three days of tinkering and headbanging to get what other team has enabled in 25 seconds flat.

To prevent such problems, JS Wiki runs a special container just for update duties for example.

I'd rather live document an installation and have an easier time in the long run, rather than bang my head during some routine update or config change, to be honest.

I document my home installations the same way, too. It creates a great knowledge base in the long run.

Not all applications fit into the scenario I told above, but Docker is not a panacea or a valid reason to not to document something, in my experience and perspective.
> Oh... so MS... but with extra steps.

Not quite: since with monoliths that are deployed in parallel or have sets of functionality behind feature flags, you're still dealing primarily with one codebase and each instance should be able to service requests on its own, instead of making further network requests across N other instances.

I actually wrote more about this a while ago, "Moduliths: because we need to scale, but we also cannot afford microservices": https://blog.kronis.dev/articles/modulith-because-we-need-to...

A single codebase will generally be easier and quicker to develop against (up to a certain scale), since you don't need so much "internal glue" code between your microservices (network calls and error handling, data type marshalling etc.).

That said, personally I'd prefer microservices for other reasons - so that I could let old parts of the overall system (possibly developed by others) not get in the way of progress, such as not being able to update the application/service to JDK 11/17 because of a PDF library only runs on JDK 8 or something like that.

Furthermore, if you work on a project for long enough, the slow startup and compile times of a large monolith (without the modularization at least, which might not be possible to ensure in certain stacks), the high resource usage and possibly sluggish performance, the numerous approaches that have been utilized to get something like logging or scheduled processes over 5-10 years of development clashing with one another and many other things will just get very annoying and painful to deal with.

Being able to spin up a new service with whatever is easy to work with for the particular case, making it your own little corner of the overall system with good tests and arguably good code (at least for now) is really nice. Until you have 20 of these services, written by people with varying approaches/standards and it's a mess again.

I think there's really no winning with either approach, each has their benefits and shortcomings.

> not to mention we usually care about the DB scale also, which is harder to scale as a monolith with segmented traffic.

This is a fair point!

Though I think that GitLab recently split their database across the boundary of CI functionality and everything else, which was a pretty good example of how far you can get with a single DB (no doubt with replication/clustering and standby instances though): https://about.gitlab.com/blog/2022/06/02/splitting-database-...

In contrast, forgoing something like foreign keys and ending up with distributed transactions (sagas or similar), having to enforce your own data consistency etc. can be asking for trouble before you actually need to care about scaling and split everything up so much.

It's probably a matter of choosing whichever approach works for your scale now and will work for you in the near future.
I'd be more careful when using the word "amazing".

I agree that technically it's well done, but IMO it leaves too much space to McNamara to write his own narrative.

McNamara's role in the escalation of Vietnam War and the U-turn he did in the Senate hearings towards the end of his term as Secretary of Defense is something he IMO never properly tried to reflect upon...
> so these assholes sink

That's uncalled for. You're letting your envy through.
As I always do when yet another UI option comes along, I went looking for a hierarchical "tree" view widget in the documentation.
Could not find it.
My crazy advice: Build a monolith as microservices.

By which I mean focus on Domain Driven Development, focus strongly on modularity even when, and this is the key part, it's not required because it's in a monolith.

There are a great deal of advantages to microservices like teams being able to focus on a subset that can still be accomplished with a well designed monolith. While still avoiding the biggest headaches with microservices like managing a crazy network of deployments, across multiple environments where teams don't have the neccessary discipline to communicate.

If at a certain point scalability does become a big enough issue, then it's much more manageable to segment what's needed (and even transition back if needed). It still might take months, but the quality of the transition is much higher.
It's an option when "The source will run out eventually" which is what I replied to.

Synthetic fuels were used in WW2 by the Germans.
I learned that Stable Diffusion can read! It's called a "typographic attack". https://www.theguardian.com/technology/2021/mar/08/typograph...

For example, this site lets you create variations on an image that you upload: https://47725.gradio.app/

Feed it an image of text (type text in a paint program and save as PNG), and it seems to understand some words. https://i.imgur.com/aXELmHo.png
It's cheap compared to a Trinnov system. But honestly you might be better off spending 300eur/usd on wood, Rockwool and some fabric.
Gotta keep the "devops" teams employed, though!
It’s not, that was debunked.
It's not necessarily much in the way of extra steps. The Elasticsearch Cloud-on-K8s operator IMO does this quite well.

You define 'node sets' which each play a role in the cluster. Node sets can have tags applied to them, and this affects the procedures they run.

For example, you could say:

1. Let's have a node set of 3 master nodes.
2. Let's have a nodeset of 10 hot data nodes, backed with SSDs and tagged with 'hot'.
3. Let's have a nodeset of 5 cold data nodes, backed with HDDs and tagged with 'cold'.
4. 4 client nodes for load balancing.

You could also say - let's have 3 nodes that play all roles.

On startup, each node starts only the parts of the app that correspond to the roles it's playing.

It's fairly seamless and I think this model would expand quite nicely to 'business logic' services

Anecdotally, have seem some people attempt to retrofit a poor man's version of this model into their microservice in response to e.g. performance problems.
Hey there, yes the only thing collected is authentication so email password signing in via Firebase. It isn’t used in any way other than auth. Hope that answers your question!
I think the important thing when beginning to aquire any skill is to just start doing things so you can understand the medium. After you've actually gained familiarity with whatever it is you've been learning, then you start reading tutorials and the like. That's when they'll actually make sense and you can internally apply the concepts they teach.

If you absolutely must have structure to your initial learning, I've heard good things about drawabox. Though they suggest starting with physical paper and pens.
I can confirm, just down the street there are two mobile homes. (Within less than a few minutes walking distance, before they were evicted, one of these homes had several instances of domestic violence, repeated calls to the animal control who on entering the house found several dogs days into starvation eating their own feces from hunger (they also would growl and bark at anyone attempting to walk or bike down the road). They were close enough that every so often we could hear the angry yelling for hours on end as the woman and her partner(s?) would fight. The other one, while quieter has approximately 3 unused vehicles, assorted junk, and lots of other good stuff dangerously close to spilling on to the neighbor territory, I'm living in a very rural state and can assure you this is the norm
Honestly, never expect browsers to support them to begin with anyway.

Any semi-serious FTP users use dedicated clients.
The diode lasers probably aren't worth your time.
> What's wrong with it ?

It relies on lining up pairs of values in a way that cannot be checked by the compiler rather than having dedicated functions that ensure they are kept together.

This is the fundamental difference between bad logging libraries (like klog, hclog etc) and good logging libraries (like zerolog).
I've wanted this for a long time, and it makes a ton of sense. Thanks!
2015 was the year of FP. Haskell was all the rage, elm was hot, large scale dismissal of OOP was in the air. To be clear I don’t think FP or OOP are really fads but their popularity waxes and wanes. I’ll see y’all in 2027 when static typing is whack and everyone is going back to dynamic typing.
I wonder if this could be somehow tied to global warming. Maybe the Jetstream weakening or ocean currents changing. Or is it just a fluke?
Left shift with a negative shift count still has UB issues unless you generate inefficient code. The way the shift count is read is different on ARM, x86 scalar, and x86 SIMD… so you can't autovectorize it without UB.
And where do you think the materials to make solar panels come from?

They come from mines.
Well done you, I guess? Nothing to disagree with. I'm just amazed this can be actual reality :)
5ish years, here (though out of the industry for a bit). Why do you recommend against the new gTLDs?