skysight-inc/HackerNews huggingface dataset:
I told myself I'd stay off this site because there's so much distracting crap on here but I need to correct this one.

You don't need a notification broker unless you want to run non-free garbage. Well written apps will just service the socket they get data from just fine. This is already the way things work on Linux, the only thing missing for real time notifications is to have the network interfaces wake the device up instead of relying on eg rtc-wake.

>centralized server infrastructure that costs a lot of money to develop

Maybe but Mozilla seems to get away with doing it for free and they have way less money.

And the higher level comments are right. AOSP is absolute fucking garbage. Before Android 5 it wasn't clear if this was something intentional from Google but it's clear now. They hate people having control over their devices and are in many ways even worse than Apple here despite publishing some code.

>100% purity

Purity will be the only thing that results in success. Already the Pinephone works well enough for people who are used to desktop Linux (sans the hardware issues with the modem.)
I am not a TDD person, but when you write some code you want to see if it works. So you either write a unit test, or you plugin your code and do the whole song and dance to get execution to your new code.

I see TDD is REPL driven development for languages without a REPL. It allows you to play with your code in a tighter feed back loop, than you generally have without it.
The guy created a $4 billion business that changed the game for co-working spaces. He just made the mistake of convincing people it was a $47 billion company, and Soft Bank threw fuel on the fire. (and he did some weird shit with the IPO)

What he accomplished is still incredibly difficult, and by all accounts he has a rare skill set for getting people excited about a vision. Plus, his failure mode is widely known now.

I'd throw money at him if I had some to throw, for sure. Don't bet against crazy and smart.
If Pine had targeted Android AOSP, I would have had zero interest in their product. I suspect I'm not the only one. Instead, I bought their pinephone because it could run Debian.

I went from Maemo (Debian based) to AOSP Android when my n900 no longer worked. I've never experienced such a user-hostile platform as Android-- you even have to expend effort just to gain and retain root on a device you nominally own. And, I don't trust anything in the Android ecosystem to not be spying and tracking.
tl;dr: Once your phone has ever booted the Android 13 bootloader, if it ever tries to boot an older bootloader again, which is easy to do by accident while doing ROM development, Google permanently hard-bricks it.
I wonder if the filter was embedded in the firmware of the CODEC's internal DSP (as it should) or simply done via software driver. For the latter it would mean the user would have to download the custom driver from the laptop manufacturer's website to get the fix as a generic driver would not have it. This would also mean that people using Linux distros on that laptop would not get the fix as well.

Though in this case the filter would not prevent crashes if the song was played externally, like from another device or over a PA system.
I've had some success cold emailing researchers and asking about openings in scientific computing. Worst case they just say no. Also look at university corporations, e.g. AUI, UCAR/NCAR, etc. They sometimes hire staff programmers and/or contractors to farm out to federal agencies. Universities themselves may also post staff developer positions; these can be an entry point into a scientific discipline if the role allows you to make connections with people in the field. Another option is government agencies themselves, e.g. in NIH and CDC I think there is some recent demand for bioinformatics developers.

It's probably better to identify an organization you're interested in first, then look at their job boards. Aggregators likely won't list as many of these roles.
The posture of what, scientific media reporting? Nearly all papers that I've read generally state confidence, needed work, and confounding factors
Depends on what you're looking for.

Do you want standard English syntax, grammar, punctuation and capitalization, with simple words, short sentences and coherent paragraphs? Cory does this well.

Or do you appreciate an eccentric, experimental style where structural idiosyncrasies complement the text?

Do you want a straightforward, linear transcript of the plot? Cory does this well.

Or do you want a meandering exposition of the inner lives of the characters, where the plot emerges from a faceted exploration of multiple perspectives, not all of which are accurate or reliable?

I read Cory's stuff for the ideas more than language or technique.

For example, his book "Walk Away" applies concepts from open-source software development and extends them to the physical world.

If you don't like the features or direction of a project, fork it and make it what you want. If you don't like your town or neighborhood, walk away and build a new community the way you want it. No need for stress or conflict or violence, no need for coercion, just walk away.
> usually that crime is murder.

There aren't many blown up airports by people that stated such things on the internet, this is not a rational concern.

I think people in the UK got sentenced for having bad taste too where bad taste is a matter of perspective.

We completely revamped air port security specifically to provide a feeling of safety after 9/11.
I think new languages with sufficient popularity (go, typescript, rust, dart) do it pretty well.

Old languages also have gained good tooling, but IMO the problem is that they are not as well documented as in-built systems of newer languages.
Gigahertz weren't inflated per se, but there were similar effects to the name games with process nodes with clockspeeds when those were more directly seen as indicators of performance. I'm thinking particularly of AMD having Athlon model numbers that were 1:1 to clockspeeds for years, then Athlon XP switching to ones that were above their actual speeds, to sort of vaguely indicate which Intel clockspeed they were claiming performance parity with.

Of course once they were beyond the clockspeed-above-all Pentium 4, Intel themselves stopped focusing on marketing clockspeeds and things gave way to basically arbitrary naming/numbering schemes. (Or to some extent, core counts.)
You've gotta just keep putting coins into the slot machine, after all, probability dictates you can't lose forever :)
I hang up on people all the time. I don't want to spend minutes of my life answering probing questions. Just hang up as they speak.
I'm not sure what you're getting at. The definition of a free market is one in which private corporations can do what they want without government regulation; the more laws there are which regulate business, the less free the market is. So saying that a law which splits companies once they reach a certain size makes the market freer sounds like an oxymoron to me.

It would certainly have the potential to make the market work better and improve competition, but that's not what a free market is.
I have fond memories of using Borland's Delphi when I was a much younger boy. GUI building tools such as Delphi, VS, JavaFX and the old Dreamweaver really helped certain concepts click for me at that age.
This is really neat, I have been keeping an eye on Supabase, this (presence) is the feature that will finally push me to build a side project with it. I have one in mind.

Anyone from Supabase here, do you have any plans to build in support for CRDT toolkits such as Yjs or AutoMerge for these features? It would make working with them so much easer if there was a plug and play backend.

The one other thing I would love to see next from them is an offline sync product, so you could partially sync a users dataset to their device and save back any changes later (bonus points for then combing that with CRDTs). Maybe the WASM Postgres yesterday [0] could be a foundation for such a product.

https://news.ycombinator.com/item?id=32498435
> How would you look at someone using a single key for their car, house, safe, work place, and so on?

This is a terrible analogy, and I don't see any other justification for this setup.

An SSH "key" is also referred to as an "identity". Contrary to a car key, it is not tied to the car, but to the client's identity. It is more like a badge than a brass key.

A car key has the limitation that your lock can only accept one key, and can't be easily updated to accept/refuse keys. You also can't remotely give somebody access (you have to hand them the key) and you can't prevent someone with the key from making a copy without returning it.

An SSH key pair has none of those limitations so it's really not clear why anyone might want to manage them like car keys. If anything, the root password is more like a car key than a key pair is.
From my understanding, 3 nm refers not to the size of the gates in transistors, but to the resolution at which they are printed.

Similarly printing text at 600 dpi doesn't mean that the actual width of the stems in the letters is 1/600 of an inch.
Denmark's farming industry's ERP system run on a system called Ø90 which is written delphi, java and cobol. Still being actively maintained by IBM today.
See my other comment below. I don't recommend doing it all the time specifically because with experience you can often skip a lot of the rgr loop.

> Everyone understands the idea, it's just a massive time sink for no more benefit than a test-after methodology provides.

This is not something I agree with. In my experience, when TDD is used you come up with solutions to problems that are better than what you'd come up with otherwise and it generally takes much less time overall.

Writing tests after ensures your code is testable. Writing your tests first ensures you only have to write your code once to get it under test.

Again, you don't always need TDD and applying it when you don't need it will likely be a net time sink with little benefit.
Super evil
Smoothing is used to negate seasonal effects.

Suppose you run a bar, and your busiest days in order are Friday, Saturday, Thursday, Sunday, Wednesday, Tuesday and Monday.

Now you are the owner and you want to look at your foot traffic everyday to monitor the health of your business. However, from the ordering I've presented, this will almost never work trivially. Monday traffic will always be less than Sunday, does this mean every Monday you should be concerned about business? Of course not.

However by averaging the last 7 days and looking at that each day, you are canceling out these seasonal effects because every single day of the week is accounted for in your measurement. If the 7 day moving average on Monday is less than Sunday you should be concerned because the average when calculated on Sunday included the pervious Monday.

For your example, you use the smoothed data and a history of the original data to come up with an exact explanation of which days are the best.

For example if you are a bar owner and you don't know which day is the best, you can take a 7 day moving average and subtract it from each day of actual observations. Then averages those differences grouped by day of week and you get an estimate for the day of week effect (you can also calculate standard deviation as well).
hey hn, supabase ceo here

we're excited about this release - it adds a few neat features to our Realtime server[0]. For those who don't read the post (it's quite long), our Realtime server was initially built for subscribing to Postgres changes via websockets. We've added Broadcast functionality (for "ephemeral" messages that don't need to be persisted to Postgres) and Presence (similar to Broadcasts, but it retains an eventually-consistent state between users).

We were planning a larger write-up with all the technical details but it became a bit long. Some highlights:

- Realtime is built with Elixir an Phoenix[1]

- We've moved to a single, global cluster
- We're using `Phoenix.Tracker` to globally distribute the Erlang PIDs of all of our Postgres connections. This guarantees there is only a single connection to each database.

- We've implemented a "leaky-bucket" rate-limiter using Erlang's `:counters` module[3] for "per tenant" rate-limiting. We'll move this to a global rate-limiter in the future

- We're currently seeing ~2000 concurrent connected users - it will be interesting to see what this spikes up to now that this is on HN

It's still in heavy development, and we'll make sure to detail all the choices we take as we continue solve problems. A few of the Realtime team will be here answer questions - @chasers, @wenbo, @abc3erl.

[0] Realtime: https://github.com/supabase/realtime

[1] Phoenix Framework: https://www.phoenixframework.org/

[2] rate limiter: https://en.wikipedia.org/wiki/Leaky_bucket

[3] :counters: https://www.erlang.org/doc/man/counters.html
+1 on "well defined spec" -- a lot of Healthcare integrations are specified as "here's the requests, ensure your system responds like this" and being able to put those in a test suite and know where you're at is invaluable!

But TDD is fantastic for growing software as well! I managed to save an otherwise doomed project by rigorously sticking to TDD (and its close cousin Behavior Driven Development.)

It sounds like you're expecting that the entire test suite ought to be written up front? The way I've had success is to write a single test, watch it fail, fix the failure as quickly as possible, repeat, and then once the test passes fix up whatever junk I wrote so I don't hate it in a month. Red, Green, Refactor.

If you combine that with frequent stakeholder review, you're golden. This way you're never sitting on a huge pile of unimplemented tests; nor are you writing tests for parts of the software you don't need. For example from that project: week one was the core business logic setup. Normally I'd have dove into users/permissions, soft deletes, auditing, all that as part of basic setup. But this way, I started with basic tests: "If I go to this page I should see these details;" "If I click this button the status should update to Complete." Nowhere do those tests ask about users, so we don't have them. Focus remains on what we told people we'd have done.

I know not everyone works that way, but damn if the results didn't make me a firm believer.
Journey to Lumen
That tick-tock model actually illustrates that it takes significant work to re-do the physical layout of a design for a new process node, even if the higher-level microarchitecture design remains unchanged. You don't get the benefits of a full node shrink for free.
I'm think it's a combination of nostalgia and familiarity. Those were the kinds of UI's I used when I took classes about computer programs and spent a lot of time independently learning programs.

All those hours spent makes it feel more comfortable though it may not actually be better.
One typical use for a rotary encoder is volume control.

The sticking-upwards knob makes the keyboard harder to transport though. It definitely risks to be broken off when put into a backpack.
This is a topic I find interesting. Out of any society in the world, in some form or another there always emerges some de facto leaders. And in some places in the modern world they will adopt democracy only so much as they know they can "win" elections and harness goodwill from other democracies. In some places being directly involved with the government is the only way to live with some luxury.

Main thing is I think there has to be some sort of cultivation of democracy (and some associated values), or it's just a facade or mob rule. It seems easier if the citizens are already middle-upper class for instance. We underestimate how much people need to be "primed" for democracy for it to flourish, it's also a more active process ideally that requires engagement, which isn't always so viable.
I kinda feel like half of the message here is “We listen to our community, we just don’t always act on it.”

I realize that’s healthy, but the way they’re going about it makes me feel like they’re trying to weasel out of it or something.

I’m left with a mild feeling of disappointment and I’m not sure why.
Full title: Linking the nonmaterial dimensions of human-nature relations and human well-being through cultural ecosystem services

WaPo article about it with a few quotes: https://www.washingtonpost.com/climate-solutions/2022/08/05/...

Web Archive of WaPo: https://web.archive.org/web/20220818151446/https://www.washi...
Sounds to me like if you avoid heating them it's fine, which means there should be no issue with dietary PUFAs.
> the anti-Agile crowd ... replacement methodology ... has no name ... lots of people dislike Agile

AIUI, there is no capital-A "Agile". It's a pilosophy, a mindset, a set of methodologies, not a brand or a product.

I actually think that could be a heuristic: Talks about capital-A "Agile" == doesn't get what "agile" is about.
thanks - fix going out now
I knew a pharmacist who wrote his own POS software in Delphi. It (and Visual Basic) had that position where they were so usable that even someone whose fulltime job was something else would be able to single handedly make a line of business app for that business.
Cannibalized from the bottom by Ryzen and from the top by Epyc (aka Threadripper Pro).
I mostly used to Matrix already. I prefer the way they work and I prefer their approach.
A better question might be why is a company considered a legal entity or even a technical entity? It has been said that they shouldn't be and that legality should rest with the individual companies' owner. This of course would end corporations and much of the crap they produce and force owners to be accountable to their word. Yes, a novel concept.

But don't take my word for it. Read what Adam Smith had to say about it first in the Wealth of Nations.
https://www.ibiblio.org/ml/libri/s/SmithA_WealthNations_p.pd...
How to write that one test without the iterative design process? That's something always missing from the TDD guides.
I haven't counted them, but the corresponding electronic music page has a lot: https://en.wikipedia.org/wiki/List_of_electronic_music_genre...
It wouldn't be the first time though that Apple used different process nodes in the same chip "generation".

- A5(X) 32nm and 45nm
- A9(X) 14nm and 16nm
- A10(X) 16nm and 10nm

If apple wanted to use N3 for the A15 or the M2 then they'd have designs pretty much ready but due to TSMC delays didn't roll those into production.

I'm pretty sure Apple does a few designs in parallel and react according to what the supply chain and market conditions allow.
This has been rehashed a million times.

My view is that TDD is great for non-explorative coding. So data science -> way less TDD. Web APIs -> almost always TDD.

That said, one of the things I think the vast majority of the leans anti-TDD crowd misses is that someone else on the team is picking up the slack for you and you never really appreciated it. I've joined too many teams, even great ones, where I needed to make a change to an endpoint and there were no functional or integration tests against it. So now I'm the one that is writing the tests you should have written. I'm the one that has to figure out how the code should work, and I'm the one that puts it all together in a new test for all of your existing functionality before I can even get started.

Had you written them in the first place I would have had a nice integration test that documents the intended behaviour and guards against regressions.

Basically I'm carrying water for you and the rest of the team that has little to do with my feature.

Now there are some devs out there that don't need TDD to remember to write tests, but I don't know many of them and they're usually writing really weird stuff (high performance or video or whatever).

But I have stopped concerning myself with changing other peoples minds on this. Some people have just naturally reactive minds and TDD isn't what they like so they don't do it.
Emacs: Ef-themes demonstration – Protesilaos Stavrou [video]
I work for a large chemical company and we only have a single DGX
It's a bit hard to find something. Usually, people who contribute do so because they're users of a project and want to fix bugs or add features, so that's one way.

Other than that, most of my open source work was just created by myself. If there's something you think could be useful or interesting, just make it and open source it.
New warnings appear in -Wall with just about every compiler upgrade. That's why standard advice is to never ship with -Werror because the next guy's compiler may fail to build it.
World’s fastest airliner ‘Overture’ to usher in new era of supersonic travel
I appreciate the response, no hard feelings. Your take was fair. I definitely don't want to dog pile on what is otherwise a warm spirited submission, but something about Guix is grinding my gears! In hindsight, this submission is the wrong forum for such a rant.
I think it's mainly for investors yea. They don't want people reading articles to see that the competitors numbers are better than theirs.
The risk that TSMC doesn't deliver on node improvements / deliver the relevant SoCs in the required numbers.

And if you think that risk is small / nil I would point you to Intel's recent track record.

And just to point out that Apple actually does bear the risk you've highlighted as Itanium was a design (which Apple does) not a manufacturing failure.
You should be reading "3 nm" as "3 nm equivalent". It doesn't mean anything is 3nm, it's just the simplest way of expressing transistor density without making people transition to a different measurement they are not used to. I would personally like Tr/μm², but I'm fine with nm too.
How is joint military exercises with Russia not hostility to the west?
I have never owned a mechanical keyboard but have been curious —- this design looks very sharp. I like the sleek heft of my MX Keys, this seems like it would be an upgrade. I do have a small quibble about the website though: the use of “Kailh©” with the copyright symbol. The name is trademarked, so could be written KAILH or Kailh® but never the ©.
Ask yourself to define "interesting" using concrete terms.

Are there specific fields you want the company to be in? List them.

Are there specific roles you want to be in within the company? List them.

How much of your time do you want to spend doing feature development vs maintenance? List that.

Are there specific stacks you want to be using? List them.

What size/phase of company maturity do you want? List it.

Go from there.
I think you make an important point. It used to be I'd have to worry about the OS layer, and that was it. Now I have half a dozen layers running between my code and the actual die executing instructions and as consequence of that I've lost a considerable amount of control.

The funny thing is I end spending just as much time trying to debug or figure out the other layers, looking at you AWS IAM, that I don't feel I am that much more productive, I've just taken what my code needed to do and scatterred it to the 4 winds. Now instead of dealing with an OS and the code I'm fighting with docker, and a cloud service, and permissions and network and a dozen other things.

Honestly this feels like the OOP hype era of Object Database and Java EE all over again, just this time substitute OOP for tooling.
I don't know why you were downvoted but your comment is as if I wrote "The U.S. has the highest incarceration rate in the world. I feel like in other modern democratic governments in the world the government would step in and sort out the incarceration rate."

It raises the question why you think the government would stop doing "Bad thing" if that's what the voters want.
OP here, This is a subject I've wanted to write about for years now, so I'm curious to hear your thoughts about designing Clojure codebases.