skysight-inc/HackerNews huggingface dataset:
To me, Cloudflare is essentially an early Google, but more network technology-oriented. Their modus operandi seems to be “Solve problems which can only be solved by one central actor, employ good people, do good things, and then, when everything is centralized around us…” but they haven't quite reached that last part yet. We all know what happened to Google though, so I’m not very optimistic.
I think iPhones are on a different quality level than a FairPhone so you can't compare it 1:1
even if you had saleforce it will all end up in excel anyway...
$4 GPS Tracker https://www.alibaba.com/product-detail/Mini-Car-GSM-GPRS-GPS...

+

$5 Pre-Paid SIM https://www.amazon.com/SpeedTalk-Mobile-Tracking-Locators-Wi...
https://gen.go350.com/login

https://github.com/62726164/ed25519-login

I built a website that uses public Ed25519 keys for user authentication (rather than passwords). Users sign the current Unix Epoch time (with the private Ed25519 key) and paste that base64 encoded signature into the login form.

I don't care if the idea succeeds or not, I use it for myself. I like simple, secure things and I feel webauthn is too complex.
Tech talent shortage is helping drive m&a deals
Maybe you don't lose stuff as much as other people? My brother was always complaining about losing his wallet, his keys, anything you can think of. I got him a tile, but their product wasn't very accurate. Got him airtags and the problem is solved. Not only are air tags useful, but I'm sure that there are people who would be willing to switch to iOS solely to get access to airtags. That seems pretty valuable to apple.
Pretty much anything I do for my employer. Ill make sure it works and is high quality but I am well past the stage of my career where I am emotionally invested in any of this crap.
Oh, I blow it out before I fall asleep. Was she sleeping with candles lit?
Can Cloudflare protect from websocket abuse? For example, someone establishing thousands of web sockets and sending a lot of data through them.
What isn't a footgun in the terms that you declared?

I believe people dislike OOP because the vast majority of code is written using OOP. If everything were written using data oriented programming or whatever, people would have the same reaction as they have regarding OOP.
Based on my own experience, OO works best for small, self contained concepts whereas procedures work best for the overall program architecture. Notice when OO is evangelized it's always done using self contained concepts, like data structures or GUI widgets rather than architecture. When you do use OO for program architecture, like in Java, you'll end up with lots of pointless indirection and brittle, over engineered design pattern soup. Procedures are simply more "fluid" because they are smaller, self contained and easily refactorable which is exactly what you want when it comes to program modifications.
Veritasium has a good video on how complex numbers were invented

https://www.youtube.com/watch?v=cUzklzVXJwo
React, presumably, with its approach that a UI is well described by nested functions operating on state. It's a good point. I remember long discussions on mailing lists for various FP languages conceding that UI toolkits were the one area where OOP seemed the natural fit. Haven't seen many of those discussions since React emerged.
It was a way to illustrate the metaphor: I am just as "new to the legal system" as I am at asbestos removal or car repairing... but I have enough experience with software development to understand why "tech debt" is a pretty hard concept to sell to business.

In any case my point is not "there is no tech debt if you created it yourself" it is more about "from the point of view of business tech debt is not something they care about: it is sonething they expect to just be sorted out transparently or that should not even happen".
After all, Microsoft never bills them for "tech debt", it just ask them to reboot to update their laptops, no?

I am not saying this is fair, or right. I am just trying to explain why mentioning "tech debt" falls on deaf ears.
Are you saying we should remove local state? If you aren't then why is that better organized than object state?
Every one of my projects :)
If only we could completely eliminate state! Thankfully, I am working on a plan for this. It should take around 10^106 years... give or take.

The serious comment here is that the real world imposes a minimum floor on the amount of mutable state that you have to model. Databases are giant piles of mutable state. Maybe we should start talking about "essential state" and "accidental state" the way we talk about complexity.
How is state encapsulation bad? Encapsulated state means that only a very few functions can access/change that state. Non-encapsulated state means that any code in the entire executable can change that state. How is that better?

> The real goal should be to untangle state and decouple it from computations by putting it all in global shared state (e.g. SQL, Redux, data oriented game frameworks, etc.) while using stateless functional computations to compute changes to the global state.

I kind of presume that you're in a single-threaded world. Shared mutable state plus multithreading is a recipe for disaster.
I don’t remember claiming the UI thread couldn’t be blocked by callbacks, but it doesn’t seem onerous to avoid, and it is less onerous than having to recolor all of the code in your application and every library you use. You don’t need an async and non-async version of every library in Go, nor do you need to use hacks like “.Result” that every linter likely screams about.

If you use blocking code in C#, even indirectly, you can absolutely block the UI thread, and you may do so accidentally! One async function calls another which calls another which inadvertently does some blocking computation for a few seconds only under certain conditions, freezing the whole UI. If you instead had each UI handler spawn a Goroutine and hand control back to the UI loop immediately, then you would never have any possibility of one of those “async” handlers blocking the UI loop, because every Goroutine is preemptible, and no other Goroutine is running on the locked OS thread.

That robustness alone instantly makes Goroutines better for this. A framework could easily enforce this pattern such that the developer never has to even think about the extra steps of spawning the handler Goroutine or syncing the results back to the UI thread, if there were any demand for native UI frameworks in Go, which there really hasn’t been. I’ve written somewhat similar frameworks in Go for non-GUI purposes.

You don’t seem likely to change your opinion, so I’ll just leave it there, but… the idea that async/await is suboptimal isn’t new. It’s just hard to implement something else, so it has taken languages a long time to do it. Erlang has obviously existed for a long time. Kotlin similarly decided against async/await, and Java is in the process of moving to lightweight tasks like Go using Project Loom. I’m very surprised C# hasn’t announced any intention to move in that direction.
hah, is this the return of "topmind"? I miss that guy, he was the anti-OO fanatic of the 2000s on usenet and c2.com.
Even greater their incentive to keep playing the game. Many more wages depend on that than my own. I am not necessarily calling for them being wrong, but for them playing with the numbers and presenting them in a way, that makes many people believe. They have credible deniability as well, because their tracking script didn't even run on browsers, which blocked it, so they couldn't know about those "edge cases". Only that those "edge cases" can make a significant portion of the total visitors of that website.

In the end they profit from telling everyone, that they must use GA (or similar tool) to track what is going on on the website and most marketing people will happily jump on that train, because it gives them any kind of data, which they can use to justify things, even if that data is only half the story and cannot be relied upon to give a true picture. "The data tells us so!" makes the job much easier, unfortunately often at the cost of user privacy. And so the make believe, that you must track your users with third party trackers continues and propagates. Then on the development side of things, developers or their higher ups eschew the work needed to implement first party tracking. They want that cake at no cost. Without strong ehics, the website of such an organization is doomed to disrespect the privacy of its visitors.
Spanish can be problematic due to the influence of Nahautl, Quechua, and other languages of people colonized by Spain.

But it's still a million times better than English.
Excellent 3b1b video about trying to solve wordle using information theory https://www.youtube.com/watch?v=v68zYyaEmEA
You missed my favorite iteration: Silicon Shire.
Congratulations to your parents and grandparents for being exception to this rule of thumb, and for your awareness that while you don't have any problems solved by one crypto, but that others might, and another crypto may have provide value for what you do.

Having been raised in this exceptional family might have helped :)
Sorry my bad. No, it's a web app/server :)
How are kids being around their peers "socially unnatural?" At the very least it's not more "socially unnatural" than posting on hacker news.
How did Wordle track your progress and stats before? localStorage? I feel like this change is very subtle and very user friendly for an acquisition.
It’s sad that WSJ paid this entitled, uncouth jerk to author that opinion piece. Do better, WSJ, do better. And not that it would ever happen, but Kris Frieswick will never be invited to my home… not because I’m particular about my floors, but because she’s an ass.
This is a funny tweet, but in some sense it kind of was. It was a mostly universal, fun, communal experience that existed for a short period of time outside the pressures of the profit motive. It was valued for its use and not its exchange, it was free to everyone, and that made it a kind of small commons.

I think everyone knew that couldn’t last. It was either going to fade away or get bought. I don’t personally know anyone who begrudges the developer for cashing out (I would if I were in his shoes), but I’m still a little sad to see the fences start going up around it.
I am actively working on improving a nearly 30 year old MUD (rewriting major systems, adding new ones, etc.). There are maybe one to two dozen players at any given time, and I don't really expect it to get much bigger. It is a lot of fun.
Oh, all of them. https://imgz.org, say. I make them for me, usually I make them available because other people might want to use them. Yesterday I made Dia[1], a small cli utility that helps you keep a work journal.

[1] https://pypi.org/project/dia/
Me as well but I was already sold on Clojure by then.
I think the AirTag stuff will eventually be limited to localized areas where the tags are wirelessly powered.
> France is the only country I know that's managed to make nuclear power work.

That really depends on your definition of "making it work". France's current nuclear fleet is already underfunded by several tens of billions [0]

Now we have Marcon announcing "tens of billions" for new reactors, the first of which is supposed to go online over a decade from now, with presidential election coming up soon.

Which begs the question; If France has so many spare tens of billions lying around to invest in nuclear, why don't they use those to cover already underfunded nuclear positions?

[0] https://www.reuters.com/article/uk-europe-nuclear-idUKKCN0VP...
Is that supported by any password managers? :)
A program with only immutable data cannot do anything interesting, almost by definition. Some data has to be mutable.
"Nothing can ever happen for the first time."
I think it does but not always. It works now, thanks!

I don't know if you've seen

https://news.ycombinator.com/showhn.html

one of the things it talks about is minimizing 'try it' friction and this one felt pretty high, even without the password thing. People bounce at not just account creation but also stuff like 'beta access' especially if it's not clear from the 'beta access' verbiage if it means 'access right now' or just ending up on some list.
You were transferring dicom files out of country? Madness. That's identifiable medical data.

Tell me you were at least running anonymisation software in hospitals before you transferred?
https://enso.sonnet.io - I have perhaps 10-20 regular visitors per day.

I’ve been writing with it every day for the past two years and I generally suck at sticking to new habits, so I’ve been happy with it so far! It’s my favourite project that no one uses.
This supposedly proves that humans are much better tracking social contracts than arbitrary, abstract ones. But I feel like it's actually the wording that makes the puzzle hard. We don't think:

> If somebody is drinking beer, they are 21+.

We think:

> To drink beer, you must be 21+.

And if you formulate the other puzzles in the same way, they are much simpler:

> If a card has a circle on one side, it must have the yellow color on the other side.

Is this your impression too? (Actually, after writing this comment I realised I hadn't checked the red card... But I also hadn't checked the 17 yo lol.)
Like the wealthy Bay Area town that just recently sought to block the development of affordable housing under the pretext of protecting mountain lion habitat.

These people would literally rather live next to mountain lions than next to slightly poorer people. (ignoring the fact that mountain lions don't actually roam bay area suburbs)

https://sanfrancisco.cbslocal.com/2022/02/07/woodside-offici...
Absolutely. I really want to love FP style programming, but I just can't get it to gel in my head. I'm totally on board with the concepts of side effect free programming, minimising state, passing around functions as parameters, etc...

But I struggle with reading it, and I struggle with writing it, and I struggle to build a conceptual framework of how FP style components fit together. I've been banging my head against the FP wall for _years_ now, and I still can't seem get a level of fluency that where I'm comfortable using it regularly.

That doesn't mean FP sucks, it just means my brain isn't wired that way.
Knife purchases are controlled in the U.K.[1] Persons under 18 are not allowed to buy knives, but in practice this means most people are showing an ID to purchase a knife.

[1] https://www.gov.uk/buying-carrying-knives
I thought it had wiped all the scores because I already played today's. But I think I must have played it during the migration period or something because it was the same word, and after getting it my previous stats are there.
I’m not familiar with any company that does this wittingly.

It’s extends confidential internal data, without context and exposes the company to litigation risks otherwise avoided by a firm ‘no comment’ policy.

For employees at an officer or director level, their job titles are already disclosed via mandatory SEC and other required disclosures.
Very often in code like that you see "struct" types filled with function pointers.. Those are literal OO "vtables", just implemented manually instead of being generated by the compiler.

The Linux kernel is huge, yes, and is written in a "pre-OO" language. It's also full of OO paradigms.

For example, the core kernel developers don't want to have to write huge "switch" statements to handle the thousands of different drivers written by tens of thousands of third-party developers.

What do you expect to see at this API boundary? Perhaps.. and OO API with vtables and everything?

Yup: https://www.kernel.org/doc/html/v4.11/driver-api/infrastruct...

Function pointers in structs as far as the eye can see...
Article like this miss the question of what purposes OOP serves in practice and so fail to offer alternatives to that purpose.

In practice, OOP basically exists to take some horribly messy program, put an interface around it, and make it slightly less terrible to deal with. Similarly, it also involves creating an interface to a thing a programmer barely understands and letting the programmer do some things with it. Which is to say is about letting the programmer be wrong and only fail moderately - as opposed to making the programmer is right.

Inheritance, one of the worst feature of OOP, has wormed it's way because it's also incredibly convenient.

Everything that OOP is compared to (notably functional programming), is based on a "green fields" paradigm where everything can be controlled. And maybe those approaches work great (though you can't exhibit stuff with they replaced in OO in the trenches and maybe things great).

It's got the tone of "this suspension bridge is far superior to your roll of duct tape" - yeah, maybe you're right but that won't make the duct tape go away even slightly.

I wish someone would come up with a good and immediately applicable alternative to OOP but I can't this sort of critique leading there.
I do use a virtual DOM but I only use it to patch the HTML in the browser (no synthetic events or anything like that). The meat of it starts here: https://github.com/cheatcode/joystick/blob/development/ui/sr....

My focus for v1 is on developer ergonomics and solidifying an API (this will be frozen after v1 with the only changes being additions if absolutely necessary—a component you write today will look identical to one you write in 10 years).

All future major versions will be solely focused on performance and security (my way of saying: I haven't stress-tested renders, but for the time being it will work well for the majority of use cases).

Edit: the lack of mention of how I do it is intentional. The last ten years saw brilliant inventions turned into mush because all of the leading project devs got into an unacknowledged dick measuring contest with one another (i.e., passive-aggressive jockeying for dominance that was ultimately a distraction from building software that was usable).
vim’s text manipulation capabilities are overpowered. I can dump unstructured or poorly structured logs into a text file and format the key fields into a CSV in under a minute using no code. It’s like excel, grep, and sed rolled into one tool
https://myhikes.org

It's my own personal hiking journal that I've made public so that other folks can document their own adventures too. It'll always be there as a way to explore something new or challenge myself - either to hike more miles, more vertical feet, adding new trails, or by building new features and working with contributors. There will always be new trails to explore, map, and write about over the course of my life. When I'm old and can't get out, it'll be nice to poke through the data, revisit the places I explored, and relive memories I had with friends, family, or loved ones while out exploring the woods.
I don't now what your experience is regarding sw development (especially corporate): - in my experience technical debt is often due to:

"There is never enough time to do it right, there is always time to do it twice"
Yes please; everyone who hates Javascript needs this so bad.
No, but it would be trivial to implement that into existing ones. But since it's not a password, it doesn't seem like a good fit.
Spanish is the one I'm familiar with and there are a bunch of collisions in pronunciations like b/v and h/j (which are sometimes discernable but often aren't) along with a fair number of silent letters.
The whole conversation is a bit hard to follow, there was an issue initially, then this PR and then another Discussion that's linked somewhere in the PR. I'll let you go read those, I don't recall exactly what decisions were taken and what's the roadmap for this to become stable.

Dynamic imports are... wild, to say the least. Unfortunately they will always be inherently harder to secure, and will most likely always be treated differently than static import statements. At least that was the consensus in Deno.
Water has changed dramatically. Think of all that goes into modern sedimentation, filtration, and disinfection - not to mention treatments for hard water or additives like fluorine. The taste is better because of the mineral content, and we can even add carbonation!
> We do and no one uses it.

This is straight up denialist and hyperbolic FUD. There's a healthy and vibrant ecosystem surrounding the federated social web, which has been a thing since 2008 or so.

Also, I would argue that email's staying power isn't quite backed by the answer you gave ("it locked everyone in with its network effect") but more along the lines that it survived the Lindy effect (the great thing about this is that it's not going to its grave as a technology anytime soon).

https://en.wikipedia.org/wiki/Lindy_effect
They /can/ do whatever they want, that doesn't mean you have to like it.
Read Silvio Gesell's book or watch the silvio gesell institute on youtube. His economic theory is based on his experience of inflation and deflation crises in argentina. His son founded villa gesell.
Ask HN: How to deal with coworker code review who haven't read my code?
I started a new job half a year ago as a senior full stack engineer. There is one coworker who routinely reviews my PRs and leaves feedback that clearly demonstrates they didn't read my code closely or they didn't fully grok it. I then have to go out of way my to prove to this person the code is doing what is expected/asked, either in long winded responses on the PR, or sometimes as far as pulling them into a video call to screen share and live debug the code to them. It's becoming increasingly annoying, and even a little exhausting which is hurting my motivation and delivery throughput. Anyone ever had similar experiences or have any tips to deal with this type of situation?
Monero is what everyone used to think bitcoin was.

Now that people are starting to realize what bitcoin actually is, and all the lies and misinformation are falling away, the world is gearing up to pounce on it and fully integrate it into society. People are rapidly realizing that it really is the internet of money.

Monero will still have it's place, but only as the dark money network.

I've actually become increasingly worried that Monero is at pretty significant risk of a nation state 51% mining attack, since it mines with generic CPUs. A government could rent out an AWS fleet to attack the network and if not kill it, at least add a lot of friction via this kind of DDOSing that temporarily blocks people and breaks interest, like they do with Tor services today.
MDN documentation and Sqlite documentation stand out to me as some of the best around. The Cloudflare how-tos would be up there, if you stretch the definition of documentation
Not the same credentials, the other one. I forget what they call it, but basically we pay one bill and share iCloud storage and apps between us.
In my experience many game companies were never big on OOP in the first place.
> disrupted a foreign government's attempt to illegally bankroll the election of candidates who are politically sympathetic or vulnerable to inducements.

I must say that my first thought when reading the title was that they disrupted the market of foreign election interference.
Do you think they have accumulated complexity for no reason. Because usually evolution kicks out things that aren't needed.
And just to be clear. This is NOT a mutually exclusive solution.
Just as people use a combination of different databases for different projects and even within the same project, SFSQL can be used alongside other solutions.
It is especially convenient to use as an additional datastore when you are already storing your data in a SQL DB because there is no additional devops beyond what was already in place for that SQL DB.