skysight-inc/HackerNews huggingface dataset:
Interesting. I'm in the space (I work for FusionAuth) and I've seen the following trends:

- tons and tons of startups entering the space since the Auth0 acquisition by Okta in 2021. Probably due to a combination of: stickiness, standards, the fact the market was defined by Auth0 (so you don't have to define it or explain it), and the critical nature of it.

- providers focusing on time to market and ignoring OAuth/OIDC (or delaying delivery of standards based functionality): clerk, stytch

- providers focusing on certain use cases: workos (enterprise SSO), propelauth (b2b), clerk (react components to begin with, though they've expanded)

- self-hosting solutions with a more modern feel than Shibboleth and Keycloak (Duende Identity Server, FusionAuth, Zitadel, Ory)

- OSS providers monetizing by offering to operate their system, sometimes making it hard to find the download button so you can run it yourself

- hyper scaler solutions that are usually the default for folks building there, until limits are reached. These solutions include Cognito, Entra B2C (formerly Azure AD B2C), and Firebase.

It could be the folks I talk to, but most of them aren't interested in implementing auth themselves. They see it as undifferentiated functionality, like a database or message queue, and only worth implementing in certain specific circumstances. However, they're also worried about lock in. And they are thinking about the speed to market vs external dependency of SaaS offerings for critical application components.

However, choices really depends on team size and skillset. Startups are best served by using a SaaS offering or library framework that will give basic functionality and get out of the way so you can get to PMF and/or build features you can charge for. Bigger teams need more flexibility and have the ops skills to run auth themselves and remove the third party dependency.
> They are really unmatched when it comes to longevity and safeguarding information in a way that computers cannot replicate.

How so? There are long-term digital storage technologies that would long outlast any book and are many orders of magnitude denser.
I searched 'checklist app github' and found several free no-ai and no-login options on the top of google results.
You probably live a monovendor world for your workstation. Linux world is multivendor from the ground up.
Just a simple example in your language: app panel launcher can be provided by a software with a different origin of windows manager (as in move, resize, tile windows on your desktop). Yeah, kind of like android but this concept comes from thirty years ago.
Great point, there are situations where resistive is a lot better. I've definitely cursed my phone screen when it's raining.
I would try to find data like "tasks over 30 days old never get completed" and tie the decision (and marketing) to something like that.
Does your Wikipedia mirror include media? Text-only wiki seems a bit bleak to me, but including all media would devour so much storage, I just haven't been able to justify using that much of my limited storage space
I just make a checklist in a note on my phone. It’s accessible even when I have no network access and I can share it with people.
I do too. We are not based in the US though.
My point was that despite all the training, some whack job was still allowed to work and question voters’ rights. How many did he successfully turn away? Hopefully none, but we don’t know.
Oh yes, I totally agree with you I think this Electoral College system is absurdly complicated (and to be back to the topic, causes issues like predicting the outcome).

I shown this article because it is interesting from a "technical" perspective to see how the States are discussing together to figure out a backdoor, instead of doing what is the "right" thing: sitting on a table and amend the Constitution to abolish the Electoral College.
TVs evolved from knobs on the device to buttons on a remote (or touchscreen).

Washing machines evolved from finicky one way turn relay knobs to tactile bidirectional digital knobs with buttons for options (like extra rinses, prewash, temperature, etc)

VCRs used to be so unusable they'd blink 12:00 because no one knew how to set the time. BluRay players and PVRs put everything on screen accessible via remote or mobile app.

Smart door locks make it very easy to lock/unlock a door via phone or watch vs futzing with keys that can be easily lost possibly requiring a new lock. Much better for guests or families.

Old dial or even digital thermostats were nearly impossible to properly schedule, modern digital thermostats use phones or websites, much easier (and also visualizes all your HVAC stats!)

Smart lights let you group lights together independent of power wiring, change colors, etc

Japanese in-seat toilet bidets with dashboards or remote are masterful compared to traditional bidets with faucets.

Single lever faucets vs separate dial faucets for hot/cold water
scam site
Interesting perspective! I think HN would benefit if we shared our own mind-blowing insights here. A couple from the top of my head:

- Python: slicing, full reflection capabilities, and its use as an interface to almost anything [1], not to mention its role as an embedded interpreter (beyond the GIL debate).

- Z3: one of the closest I know for defining the ‘what’ rather than the ‘how.’ I got lost with Prolog when I tried to add more complex logic with ‘hows’, though I was a complete newbie with Prolog. Z3, however, really boosted my beginner capabilities.

- OMeta: allows me to write fast parsers without spending time resolving ambiguities, unlike ANTLR and other popular parsers using classical techniques.

- Smalltalk/Squeak: everything can be re-crafted in real-time, a blend of an OS and a programming language. The community vibe is unique, and I even have friends who implemented an operating system using Squeak. The best example? TCP/IP implemented in Smalltalk/Squeak! [3]. David Weil and I also created an early proof of concept [4] that used Linux behind the scenes, aiming to ‘compete’ with the QNX floppy disk.

- AutoLISP: a programming language embedded in AutoCAD, which I discovered in high school in the late ’80s—only to just find out that its first stable release is considered to be around 1995 [5].

- REXX on the Commodore Amiga: not only could applications be extended with this language, but they could also interact with each other. A decade later, when I used REXX on an IBM Mainframe, I still preferred the Amiga’s approach.

- Racket: I can draw in the REPL. For example with Racket Turtle.

- C++: object orientation "for C". I was not mesmerized by templates.

- Clipper: first database usage and relatively simple to create business apps.

- Objective-C: the first implementation of GCD [1], providing a C/C++ style language with fast performance, a clean event-loop solution, and reflective capabilities. However, I never liked the memory handling.

- Machine Code/Assembler on the Apple IIe: I could jump directly into the assembler monitor from BASIC.

- APL: a powerful yet complex way to program using concise expressions. Not ideal for casual use—best suited if you really understand the underlying concepts.

By the way, it’s time for Apple to embrace programming languages on iOS and iPadOS!

[1] http://www.garret.ru/dybase.html

[2] https://wiki.squeak.org/squeak/1762

[3] http://swain.webframe.org/squeak/floppy/

[4] http://toastytech.com/guis/qnxdemo.html

[5] https://en.wikipedia.org/wiki/AutoLISP

[6] https://en.wikipedia.org/wiki/Grand_Central_Dispatch
> you don’t need to understand anything deeply to know this, since it is apparent with your own ballot

Are you giving up the secret ballot in your scheme?
https://github.com/sjl/t
Is this why Google search results are so bad now?
Hack really gave PHP/Zend the kick up the arse that it seemed to need.
Somebody could invent a device that creates plastic boards with custom-designed shapes.
Intel is a huge asset, they missed major industry changes, like EUV, ARM, GPU, and splitting design and foundry. I still believe they can come back strong, but need bold decisions to regain defensible competitive advantages.
Hm wish I knew that, I just got set up in LunarVim...
Hold yourself when you hear

This is what happens when they stop teaching civics in high school. People never learn how the government works, and then when they learn one uncommon nugget of information, the only way to fit it into their worldview is to turn it into some crazy conspiracy theory.

It's pretty much the definition of "a little knowledge is a dangerous thing."
While my dishwasher has the "buttons" at the top of the door, it puts the light on the bottom, so it shines on the floor. Little red dot. Cats like that dot.
That may not be what you want. Fortuantly computers can calculate the mix you want. mostly traders care about the stoks they follow they just want someeindication if the unexpected movement they are seeing is the market or something they don't know.
It is correct in the main text in the archive.
Either this is a joke comment, or you haven't seen https://ludic.mataroa.blog/blog/i-will-fucking-piledrive-you...
Needs login
Deloitte does not hire great people. They would have to pay them great and corporate managers would rather cut themselves an arm than paying well a good employee, it is a matter of principles.
The US military industrial complex isn't nationalized.
Yeah, JavaScript has been at the core of Gnome now for years. It's brilliant IMHO because it enables the huge ecosystem of web devs to build native apps. The only thing is it's very poorly known/advertised for some reason.

It works quite well too and is very easy to get started. I've hacked together some gjs snippets a few times and it was so, so much easier for a drive-by hack than in the past trying to deal with a complex build system.
And Modula-2, now GNU Modula-2 is officially part of GCC full installation.
i don't buy that any situation is so hopeless, you're powerless to improve it. at least in the context of this field and its line(s) of work.

sounds a lot more like learned hopelessness making it harder to respond to stress with radical change because of (normal and human) fears of the unknown.

at some point though responsibility for the circumstances, the feelings, the stress -- the good, bad, and ugly or easy, hard, and nearly impossible -- has to be taken.

there's only one life to live. we owe it to ourselves and others to do more than -- to try not to -- just "roll over and play dead", so to speak.

humans have survived a lot and have adapted to just as much if not more.

if i ever allowed myself to even stay at any of my former jobs coming up in my life when i was paycheck to paycheck because of not making rent or just being flatout broke and homeless, i would have not progressed my career, or life, in any meaningful way, and just fed the negative feedback loop influencing what feels like a miserable existence (even privileged as it were).

can't hold myself hostage. and also, i can't hold those around me hostage as consequence of my non-action, either.
Speed, scale and reliability

Choose any two.
Fire that guy immediately! or, Why I'd never drive a rivian...
You can easily wipe a membrane keypad clean. Those require force to trigger the buttons, so they are not at all like touch buttons.
No problem. Don’t branch in the middle of the algorithm, choose the appropriate optimized algorithm based on the task. That’s why we haven’t had a separate fgrep binary for decades.
Exactly.

Non-citizen voting is illegal already. We don’t need new laws re-banning it.

The numbers of non-citizens voting is small so any effort to purge them is as likely to disenfranchise legitimate voters as remove illegal voters. That’s a net negative.
The GM bailout was an unmitigated disaster. Their cars are uncompetitive garbage to this day.

When they accidentally make something their customers like (the Bolt, CarPlay), upper management intervenes and discontinues it.

The US would be much better off if the engineers and factories they are squandering were allocated to other companies.
There’s no particular reason to call it a backdoor or not the “right” way.
alias tally='awk -F '\''[^-.0-9]'\'' '\''{ for (i = 1; i <= NF; i++) s += $i } END { print s }'\'''
I thought federal law required paper backups as of 2016-ish? No pure electronic voting today, IIRC.
Commentary: Time to terminate the torture of time changes – Miami Herald
> Apple had bought Tesla

lol. I think tesla was copying apple, relentlessly removing without knowing when to stop.

Apple has lost its way too in this respect.
I used to have some woollen winter gloves with built in touch-screen fingertips. They worked well, but also made things quite slippery when holding a phone. This once resulted in a shattered screen when the phone slipped out of my gloved hand and flew onto a cold, hard, London pavement…
please add go clock to (additional time)
History doesn't repeat, it rhymes; and it kind of goes in phases or epochs. As Derrida was wont to point out, we show up in the middle of things, just flippantly speaking a language and carrying on as though the language was something we were born with and it's been the same forever because we only know our own "forever".

I popped my cherry on VAX silicon, where stack frames were baked into the silicon. This meant that regardless of language, the stack architecture was a target for the compiler not something it constructed. I fell into the middle of things: VAX silicon was new, and people wrote in e.g. COBOL, FORTRAN, BASIC, Pascal, C because they'd successfully done so before and had libraries and practices which had stood the test of time and had made the jump to successfully infect a new species of silicon.

The successful colonizer libraries and practices had certain rules. "You can't manage heap in BASIC" for example, or that modular compilation units all had to be written in the same language. This is not and never was strictly true, and the people writing code knew it; but it was true enough for code which jumped silicon.

I on the other hand knew about the silicon stack, and could implicitly understand some of the more esoteric compiler pragmas for dealing with that stack (intended for cross-language linking support) and so by disabling certain linker checks and abusing compiler pragmas I could do e.g. memory management in BASIC by isolating the compilation unit where "memory is an array" from the one where "a memory address is an integer" and explicitly telling different lies with compiler pragmas in each.

Fast forward a few years and everybody had learned HTML and then I'm confronted with somebody wanting me to fix a steaming basket of soup machine gun sprayed into different files all with "(c) Macromedia" in them. "Where's your no-code tool which generated this?" I innocently ask. "Wuuut?" is the response. Yea well when you find it, let me know. Let's just say the people who have to fix things like that probably get paid good money and the solves they come up with are comparatively fragile, that code will not (and did not) survive; any more than my silicon-aware hacks (which I was paid quite well for) for VAX will work on modern silicon. Where's all of that shitty VB Wizard code spew? Thankfully gone.

Some of these integrations will not be fixable, but some of the subsystems will survive, and it might be simply because there is no security and it's possible to replay CANbus reliably as a result.
> Literally this week

N != 0, it’s less than 1/10^8 over multiple cycles. Which means zero examples in modern America of a national election being stolen through fraud.

> Blind faith

To the degree there is blind faith in this discussion it’s from the election deniers. Polls are heavily scrutinised by not only multiple layers of government, but also various outside groups, including the campaigns, as well as international bodies. One has to assume widespread conspiracy across those groups—and then be too lazy to observe a poll oneself—to conclude fraud. Not only forward looking, but worse, backward looking given the millions of dollars spent on hand recounting ballots in e.g. Arizona.

> Voter ID now

I vote in a state with a voter ID requirement. Maybe those who think these laws do something didn’t go to college. I can’t think of any other reason for the widespread amnesia around the prevalence and accessibility of fake IDs. (And you could vote with a cheap one, too. Nobody checks if they scan.)

> Closed borders now. Deportation for illegal immigrants now

About as relevant to election security as abortion and speed limits.
I worked with an Aussie who was in the US on H1B because the aerospace industry was even worse than the status quo in Australia. Last I heard he went back. I sincerely hope he switched industry verticals.
https://to-do.office.com/

Free with Office 365 / Microsoft account. Decent desktop & mobile apps too and integration into Outlook/Teams. API available via the Microsoft Graph and integration with PowerAutomate if you want IFTTT/Zapier-like functionality.

https://learn.microsoft.com/en-us/graph/api/resources/todo-o...
I find that being able to do either is best. Sometimes debuggers are amazing, sometimes they are not. It depends on what environment you are working on, what layer of the stack the problem resides in, and how complex the info is that you need to debug the problem. Being able to choose multiple paths to get information is better than locking down on one "always the right answer" technique.
a "hack", or a "workaround" is more appropriate perhaps, rather than a backdoor.

It reminds me of technical debt. Instead of rewriting the original buggy code, we add one more feature and we certainly don't change anything to the original code.

So instead we have:

"This is the logic, we do this A and this B, but oh well, anyway it's C"

Simpler is better, especially on crucial things such as elections.
IMO Next.js is overly complex for what it does.

Look at something like Remix gets the job done with much the same features.

Though I’d keep an eye on what Tanstack is doing in this space more than any project. They seem to understand the proper trade off between developer ergonomics and app complexity
The economy in tech is dramatically bad.

The national unemployment was 1.5% in August. The tech sector was %7.0?.
The tech sector has hiring freezes starting in late October thru to March.
August is the peak hiring, and the tech sector unemployment was 7%, 4.6x the national average, and keep in mind unemployment statistics only account for a rolling window of about 18 weeks give or take.

By March, that unemployment rate for tech will likely be well above 10% of the entire sector. This is unprecedented, and the downturn started in 2022 (outside that 18 week window), jobs have not increased in that time.

Subjective measures from insiders have quite a large number of tech workers describing the vast majority of their professional networks as being out of work, roughly 70% of my network is currently unemployed, and I've a few thousand people, having worked in IT for a decade in important roles.

Its wrong to claim something that is unupported/false when all external and objective signs show a serious problem. Doing this resorts to magical thinking, and delusion; definitionally.
That's a great question! And fortunately, one where you can use human behavior as a guide: if someone is actively using a checklist it seems reasonable to presume they're at least accessing it once a day. So as a quick first-pass, double that time period to two days. Also start collecting usage metrics and mine those in the future to further refine this number.
LLM Framework Leaderboard
My dishwasher has buttons on the top like this, and during the heat dry cycle the steam will activate the buttons and I'll hear lots of random beeps from the kitchen. Ponce in a while it manages to cancel or restart itself, hilariously bad design.
I was shopping at a grocery store and a lady saw me visible distraught by not being able to open a clear bag and she told me to touch some of the produce I’m about to pick up or the moisture around them. Never had the problem again. Thank you, random lady!
I can confirm the troubles with age. Another problem are cold and hot environments (sweat).

Anyway. Tactile input is generally better where an efficient placement of physical input controls is possible.

Garmin is a seldom example of a company doing it right with the Edge 840. They merged the tactile 530 and the touch 830 into one device. The best of both worlds. Guess what I prefer?

It is the Edge 530. Better screen to body ratio :)

The rise of the touchscreens are an accident. Because MBAs believe iPhone == touch == good. It isn’t. The iPhone is just small, physical switches expensive (remember the slider smartphones) and you can merge output with input (this a pro and a con). Nice when you want to zoom a map. Horrible if Okay changes the position, worse when the keyboard requires the half screen and interaction is generally ineffective.

I recommend:
https://en.wikipedia.org/wiki/The_Design_of_Everyday_Things

1. Layout your tactile interface in a way that it allows the user to create a mental model of it.
2. In best case this model exists already.
3. Make it hard to use it wrong.
4. Make it easy to use it right.
5. Also applies to the output. If the turn indicator is ON, make it ON.

PS: Right now I struggle to hide my touch keyboard. No „DONE“ or „HIDE“ and I cannot access my bookmarks for my recommendation.

Can I express an wish?

Dear device manufacturers. Please used high quality switches with travel, resistance and a click „BIPPITY-BUMP“. Add a spring. Built in a indicator light within!
The opposite side of this is unpredictable or unintended behavior from too much moisture, which in my experience has been an acknowledgement with touch screens for quite some time.

As touch screens for applications started to become common, this naturally filtered into tactical and service work fields. There is an advantage in this as it allows a more compact interface that can change more easily based on what the user needs. However the down side is, in harsh fast paced environments where the user may be moving quickly and sweating, it's much harder to register intended user feedback to the interface.

The problem is not just if touch screens should be used, but also how they should be implemented. Especially on the side of general consumer electronics, like mobile phones, iOS and Android have built in interfaces for accessibility. In some cases you can get built in accessibility out of the box with very little effort, but the reality is, it takes a decent effort in most cases to get it right and users who need this behavior are not a heavy majority. This results in a deprioritization of accessibility in many mobile applications.

This gets much worse with more hardware centric devices like thermostats, ovens, refrigerators, etc which have a higher tendency to have user interfaces developed in house and lacking any accessibility. Compounding this problem, with the popularity of touch screen interfaces, and post COVID supply chain problems, many users who needed accessible functionally were (maybe still are) left without many options, likely either having to pay a heavy premium for something with usable accessibility features, but probably more realistically, just taking what they can get.

Modern technology makes accessibility easier than ever now, and enables accessibility in places that didn't previously exist, but the lack of willingness to implement accessible features on the part of some corporations is not just providing terrible accessibility, it's taking accessibility away from places where it previously existed.
If you haven't been there, you cannot imagine how bad most car manufacturer's software departments are. They are big, expensive, and crawling with bad practices. Management usually doesn't have a clue about software, so there's a lot of maneuvering with goals being anything but producing good software quickly and cheaply.
That's what "let it fail" means. That's classical bankruptcy.