skysight-inc/HackerNews huggingface dataset:
Show HN: Clauneck – Open-Source Tool for Email Collection Using Google Search
> With his monumental work he saved so many lives.

No it didn't. The work at bletchley park was useless and had no material affect on the outcome of the war. One shouldn't get their history from movies. WW2 in europe wasn't a war of 'intelligence'. It was pure mindless slugfest between the germans and the soviets. It was the elites senselessly slamming millions of men against millions of men. The side with millions more men won.

> We are probably behind a century of progress because we lost him.

Had Turing never existed, nothing would have changed. Nothing in computing would have changed. Nothing in ww2 would have changed. It's amazing the lengths some go turn their personal heroes to gods.

1. The foundations of computing were already laid down by Post, Godel, Church, et al before Turing. Computers - from adders to 'software' driven computers - were being develop prior to or independent of Turing. Turing didn't invent the transistor.

2. The german codes were already broken by polish mathematicians, et al. And german codes played no role in ww2. The war was pretty straightforward.

Turing made notable contributions but lets not get too carried away. People act like Turing built the computer by himself and won ww2 by himself. He did neither.
Enjoy not having control over when or how your OS gets updated then.
Location: Mountain View, CA

Remote: Remote or Hybrid

Willing to relocate: No

Technologies: Python, Elixir, Javascript, Typescript, Django, Flask, FastAPI, Phoenix, React, Postgres, Kafka, Redis, Git, Kubernetes, Docker

Résumé/CV: https://rozig.github.io/resume.pdf

Email: the.ganzorig25@gmail.com

---

I am a software engineer with 6 years of experience specializing in distributed systems and backend systems. I am passionate about leveraging my expertise in a wide range of technologies to build robust and scalable applications that drive innovation and deliver exceptional user experiences.
Sounds like us tbh. So many hours wasted writing deeply technical documents that only few engineers have the background to go through, too many hours wasted on huge ass documents supporting PoCs. Ugh.
> Quite possible I’m still the junior in terms of skill though.

This is a very "senior" mindset.
What is the point of sending such a letter? Just to let them know that you are scared?
The legacy app is absolutely NOT fast if you have a significant amount of notes. Still worth using because the current app simply lacks the functionality (they "solved" the costantly freezing problem by preventing people from selecting more than 50 notes at once, for example). But certainly not fast
It's constant with regards to the length of the input array, which is the usual metric for sort algorithm performance. That is, d(runtime)/d(len(input)) can be constant, even though d(runtime)/d(max(input)) is not, if you assume that len(input) is independent from max(input) (which is inconsistent with input having uniformly distributed random members, which is probably the more common assumption).
historical repo name, it's really not that anymore, besides a very old list of marketing stuff that i rarely update. I should rename the repo, but I hesitate :)
> Like, isn't "small text blurbs" better than nothing?

I honestly don't think they are. Small text blurbs are not actually informative. You can't engage in nuance, you can't really argue a position, and you can't really have a good debate. They're just good for bloviating, and there are lots of places where you can bloviate anyway.
Your tower of wisdom must be really high if you judge Musk like this. The rise and fall of nations must lool like a kindergarten play to you.
thanks
sounds cool
And I don’t understand why that is the first thing that comes up on my Facebook feed when I scroll past reels.

I usually watch and like comedians when I am mindlessly scrolling.
Ah what happened to good ol' customer obsession AWS
> FastAPI is already being used in production in many applications and systems. And the test coverage is kept at 100%. But its development is still moving quickly. New features are added frequently, bugs are fixed regularly, and the code is still continuously improving. That's why the current versions are still 0.x.x, this reflects that each version could potentially have breaking changes.[1]

What kind of weird reasoning is this? This should be why you use actual semver, and you use the major version to indicate backward compatibility breaking changes, minor versions for new features, and patch versions for bug fixes that don't actually actually change the public API surface.

If you don't want to use semver, just don't use semver.

[1] https://fastapi.tiangolo.com/deployment/versions/
I'm not saying their implementation isn't good, it is good. And probably message-passing is the right concurrency primitive to expose at a language level for people who want to take advantage of multi-core machines running concurrent code.

I'm not downplaying anything; I'm expressing merely that with a title like "Goroutines: The concurrency model we all..." makes it sounds like go invented something new, but afaict, they're just a well-engineered implemention of already well-understood concurrency principles.
I know some friends of mine stopped using it because it requires login, and it's quicker to Google or go to Wiki for a quick answer. Most people have a laptop at work, home devices, phone, etc. So it's just you ve tried it say on your laptop few times than you are on a tablet etc so why do you need all that mess with entering email, remembering password, for what, for just a quick asking and getting answer.
The site appears to be down. Read it here.

https://web.archive.org/web/20230707193011/https://davidalle...
Hey all, TypeScript PM here.

I understand the desire here. Runtime type checking is often necessary for data validation, and we can see lots of libraries developed to help fill the gap here. But I think the fact that there are so many libraries with different design decisions is pretty indicative that this is not a solved problem with an obvious solution. We knew this going into the early design of TypeScript, and it's a principle that's held up very well.

What have been happy to find is that we've grown TypeScript to be powerful enough to communicate precisely what runtime type-checking libraries are actually doing, so that we can derive the types directly. The dual of this is that people have the tools they need to build up runtime type validation logic out of types by using our APIs. That feels like a reasonable level of flexibility.
The Math section as a whole seems very useful, especially for the self taught engineers (or people who need a quick memory refresh of the underlying subjects). The concepts are simplified enough that anyone with basic understanding of numbers can just jump in and learn what they might need regarding this particular field.

I wonder whether something like this (albeit a little advanced, considering the field's depth) exists for machine learning?
> In my experience, it's always the junior who shouts "This could all be so much simpler!"

Don't have time now to find links of Jonathan Blow, George Hotz, Casey Muratori, and many other decidedly non-junior programmers complaining about the absurd, unnecessary complexity of modern software development.

The people who complain are the people who know how much simpler it can be.

Now, there is a separate phenomenon of green devs who think they can rebuild X only because they can't fathom the bulk beneath the iceberg's tip. That is real too. But it takes nothing away from the very real fact that the vast majority of software written today is much, much more complex than it needs to be.
That boundary validation is where that kind of reflection would be useful! And it's a problem that (nearly) every useful application has to face.

Well that, and getting rid of the silly "must be able to strip types without processing them" design ideology would also enable stuff like typeclasses.
Ok, we'll add that bit to the title above. Thanks!
Yes, you need to trust your third party libraries, better check them. Otherwise they may steal your data, inject XSS, mine cryptos, have memory leaks or faulty logic.
A guide how to move to Craft
https://www.craft.me/s/Z6FdPQtMfh3KRU
Obsidian runs on a local folder of files on your device, so there are a dozen different sync services you can use including several free options, e.g. Git, Syncthing, etc.

With Obsidian Sync, your $8 don't only go towards syncing. It helps Obsidian remain profitable and 100% user-supported (no VC investors). Subsidizing costs in pursuit of growth is what got Evernote here.
The target consumer doesn't care, wasting time optimizing for space doesn't make sense in this instance .

I'm a little disappointed they didn't go purely React Native here. It would have been a great showcase as they ultimately own the React Native project.
when you land on the right tools and abstractions, your problem domain will start to feel simpler than before.
Semver specifically allows you to use 0.x for this purpose: https://semver.org/#spec-item-4

> Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

That said, I'd argue that this is a little silly. Maybe a better design is to use something I am calling "zero-calver": 0.YYYY.MM.DD. Then use semantic versioning once stability is reached.
New York Authorities Deploy Drone ‘Squadron’ to Scan for Sharks
Thanks for the source!

Although, frankly speaking, Java libraries are still the most convenient to include/extend than most other compiled languages I've seen so far. Probably because of that culture of over-engineering for abstraction/extensibility.
If your problem fits, you can sometimes keep the former version in play with the pipeline pattern, where child goroutines are stopped when the parent goroutine closes the channel in a defer when it's exiting.

That being said, my experience is that anything moderately sophisticated requires the use of for/select. In my opinion, that's fine, because select gives you so much power the somewhat more complex form is worth it.
My OCD begs that you get rid of the dot representing the day before you were born, thus fixing that final line with one lonely dot on it.
No, they're not. Threads is not a "public square" in any meaningful sense of the term. Neither is/was Facebook, Twitter, etc.
You don't need "an argument" that social class is the biggest player in determining success when the statistics have told us this plain as day for decades.
So point by point:
1. Stealing a credit card number, ccv, expiry, and name shouldn't be game over. It is because businesses want to reduce friction for customer purchases. If card not present transactions required a second step of verification, for example, multi-factor authentication, it would drastically reduce this type of fraud. Unfortunately it would also increase friction for online purchases, which is why everyone in the card processing chain is looking to shift liability away from themselves.

2. That is not the customers fault. Full stop. Yes, some sites are more shady than others, but there is nothing a consumer can do to determine if a service provider will get hacked.

3. Yes. Unfortunately, phishing is really easy. Despite the prevalence of this attack, training users to effectively detect and avoid being a victim is almost impossible.

4. See #3.

5. See #2.

6. How is a customer supposed to validate the security of an ATM against modern skimming technology, many of which are virtually indistinguishable from normal bank machines.

7. Yep, not great. Why don't banks require 2FA? Because it creates friction and increases costs. Better to just externalize the risk.

Your entire blame the user argument is bunk that has been packaged up and recirculated by the finance community for almost 20 years (and I have been using these arguments against them for nearly that long, granted it's close to ~12 years since I worked in infosec at a bank).
Probably to generate press coverage. Also to placate certain execs.
It technically is since natural hydrogen exists.

The problem with this logic is that renewable energy is regularly plunging to zero or even negative prices. Renewable leads to massive swings between excess production and massive shortages. Hydrogen is significantly more valuable than the electric used to make it, even if the end goal is just make more electricity. The best way to describe it is that hydrogen is dispatchable energy, but the energy used to make it is non-dispatchable energy. The former is necessary and will always be worth something, but the latter is often totally worthless.

That claim is purely delusional. This is a repeat of anti-photovoltaic arguments, that solar panels could never be cheap. In reality, there are simply no substantial raw material requirements preventing either electrolyzers nor PVs from plunging in cost. History will just repeat itself and the critics will be outed as closedminded fools.

Hydrogen is 10x cheaper to move around that electricity. It will be more practical to build a hydrogen infrastructure than an electrical one: https://www.brinknews.com/could-hydrogen-replace-the-need-fo...

Your article is thoroughly distorting the real story. The situation actually being described is as followed:

> Rio Tinto executive John Mulcahy told the summit that hydrogen was less efficient than batteries for mine trucks under a scenario where a miner had to produce its own hydrogen from solar or wind power.

> “Hydrogen at the moment isn’t our preference, but it doesn’t mean it is dead by any means,” he said.

https://www.afr.com/companies/mining/fortescue-and-rio-say-b...

In short, it doesn't make sense to make hydrogen on the spot when you already have access to that energy and can use it directly. But this is just one scenario, and they haven't ruled out other ones.

This is not a particular relevant situation for the rest of us. Very few people will have direct access to renewables in a remote area. It is ultimately just one possible outcome. And honestly, there's very little chance they are moving away from diesel trucks anytime soon. This is just them speculating about what they will do, not that they are obligated to actually do it.
Arnold Schwarzenegger Says ‘Terminator’ Films Predicted the Future of AI
What kinds of businesses?

Accounting firms and design firms are mostly on Yelp, Google Reviews, or Clutch.

Office furniture firms are generally on Google Reviews and sometimes Yelp.
I fully expect them to go out of business before they manage to operate their business well.

Lost opportunity.
IMO thread pools are anti-pattern in several ways. They don't globally load-balance properly and can be exhausted. I think the Go concurrency model with many lightweight threads is really nice. The only issue I have is that race conditions in Go code can violate the type system and cause horror-crashes. I've never used Go in production but have talked to outfits who do and have confirmed that race conditions are a serious issue.
Interesting. Since it does not include windowing integration at all, it looks like you pretty much have to do the glue for each platform you support. This isn't too bad, but it could be better with adapters for common choices for windowing and context management (SDL, GLFW, etc.) Speaking of which, it seems the Linux path assumes X11 for now. Wonder if EGL/Wayland works at all at the moment, but I'm not at a desktop computer to give it a shot.

That said, all of this is relatively mundane, at the end of the day. I'm curious to try it out and see how the ergonomics/performance is. It honestly doesn't look too bad and it's kind of a good sign that a large amount of the triangle example is just windowing, because the actual rendering is relatively simple and succinct for a modern graphics API. I'd like to have an adapter for SDL2/3 and support for Wayland on Linux but otherwise it looks promising. Compared to other abstraction layers (like bgfx) it appears a bit more forward-thinking in some superficial regards at the very least. (Seeing a command queue abstraction in hello world makes me hopeful, anyways.)
https://github.com/facebook/igl/tree/main/src/igl/metal
Not to be excessively negative, but this really means very little without more context. Maybe it was very slow before, or it's a particulary unused scenario. I'm always skeptical when people write such praises of their own software without giving a comparison point.
It's the setup for discussing Diablo.
From my understanding, namespaces are on the same list with enums of things that the developers regret ever adding to the language but can't take out without breaking old code. Namespaces also at least have the excuse of being a "necessary" jQuery-era "Production pattern" in the land before ESM was standardized and somewhat relating to the similar syntax sugar of import/export when generating AMD, UMD, and CommonJS modules.

So too are "experimental decorators" another thing that some of the developers seem to list as massive regrets. That example is even so much worse than namespaces because it wasn't justified by existing patterns used in Production JS at the time and that they even believed that requiring a compile-time flag with the word "experimental" in it would stop developers from using that compile-time flag in anything destined for Production usage. (Seriously, we all should shame the many projects/companies that did that.)
New Proposals Would Allow UK Spy Agency to Monitor Internet Logs in Real-Time
Nanite renders small triangles faster by avoiding the dedicated hardware and using compute, instead.
It's 11PM and the unclosed curly bracket here is going to prevent me from sleeping.

Did you mean
```
{"foo":{"bar":"baz"}}
```

?

By the way, have you had success at asking GPT to generate unit tests that include edge cases? I've been wondering about that.
To each their own! I have a protected bike path all the way from my home to work:

https://www.seattle.gov/transportation/projects-and-programs...
I get it. People feel the pain correctly but decide the solution is some combination of write everything in shiny new framework and start linting more strictly.
"The number of people visiting AI chatbot ChatGPT’s website and downloading its app fell". That's the article's byline, to me that's quite clear they are talking about publicly available stats, not some internal metric of users or API usage.
> ig_signals_cupid_better_recall_v1.mlmodelc

Are they using on-device ML? Why?
I'd have a fucking aneurysm if someone tried to pass off those commit messages at work.
A FactoryFactoryFactory in Production (2017)
SF Declared Dead, Full of Drugs and Homeless, Multiple Times in Last 50 Years
Coming from django primarily, but written some flask code. I would say the ecosystem. As of my last try, adding authentication (via cookies) to a fastapi project was somewhat cumbersome.

Usually as the projects grow, and I start reinventing the wheel, I come to regret not going for a "full" framework.
And that margin call might come at a bad time
He flamed out, then is back after Lisa Su called him (lmao)

https://geohot.github.io/blog/jekyll/update/2023/05/24/the-t...

https://www.youtube.com/watch?v=Mr0rWJhv9jU

https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...

https://geohot.github.io/blog/jekyll/update/2023/06/07/a-div...

On a personal level that youtube doesn't make him come off looking that good... like people are trying to get patches to him and generally soothe him/damage control and he's just being a bit of a manchild. And it sounds like that's the general course of events around a lot of his "efforts".

On the other hand he's not wrong either, having this private build inside AMD and not even validating official, supported configurations for the officially supported non-private builds they show to the world isn't a good look, and that's just the very start of the problems around ROCm. AMD's OpenCL runtime was never stable or good either and every experience I've heard with it was "we spent so much time fighting AMD-specific runtime bugs and specs jank that what we ended up with was essentially vendor-proprietary anyway".

On the other other hand, it sounds like AMD know this is a mess and has some big stability/maturity improvements in the pipeline. It seems clear from some of the smoke coming out of the building that they're cooking on more general ROCm support for RDNA cards, and generally working to patch the maturity and stability issues he's talking about. I hate the "wait for drivers/new software release bro it's gonna fix everything" that surrounds AMD products but in this case I'm at least hopeful they seem to understand the problem, even if it's completely absurdly late.

Some of what he was viewing as "the process happening in secret" was likely people doing rush patches on the latest build to accommodate him, and he comes off as berating them over it. Again, like, that stream just comes off as "mercurial manchild" not coding genius. And everyone knew the driver situation is bad, that's why there's notionally alpha for him to realize here in the first place. He's bumping into moneymakers, and getting mad about it.
ServiceNow Insecure Access Control to Full Admin Takeover
Discussion: https://news.ycombinator.com/item?id=36616037
Well, you do you. Vaya con Dios. I hope you can get rich & happy!
Heat waves, scorching spells, welcome to rising Celsius of climate change
One in three UK vegan products found to contain milk or egg
Is there a source other than Twitter? I cannot / refuse to load links from there.
This is semver:

> Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

(from https://semver.org/)
Sure it makes sense that density per neighborhood would vary for testing and in the future will vary by demand.

Any new technology is going to have challenges as it scales. I think the expectation that the system is only used in public once its perfect is extremely ideal. The systems are doing really well at being safe (there are no human deaths linked to AVs nor any severe accidents despite over 1 million + miles driven).
What's this "awkward inner platform language"? They are asking for a `typescript.generateRuntimeType<T>()` function to be native to the language. Well plenty of libraries provide exactly this syntax today. Here's tst-reflect: `const type = getType<T>()`. Notice any difference?
This is what happens when you play games. Sometimes you lose, and you have to pay. I can see Musk or X Corp. or whoever losing this case, being countersued, and having to pay more.
Everyone needs to learn to do calculus by hand before advancing to the calculator. People picking up frameworks without fundamental understanding is a shockingly common fallacy.
Spoiler alert - it's a cheese omelet with chips. There is nothing unique about this recipe.
I think you're missing my point. The early Ruby and Rails community I remember was a collection of very smart and explorative programmers who wanted to build cool stuff with this interesting language. People were trying out DSLs -- sure they could've used LISP -- but Ruby's metaprogramming was inviting and was a reason for the succinct Rails syntax which was a selling point compared to say Java's cumbersome approach.

The speed of trying stuff out (even if it wasn't super efficient) why startups used it. So it was a community of highly productive people sharing their love of building new things. That's my memory of that time period.
Agreed. The housing crisis has been decades in the making and we are so far past any one solution being able to make any meaningful progress. We need 15 solutions applied consistently over the next few decades, including making sure housing units are not taken off the market to be used as short term rentals on Airbnb. I have no problem with people making some extra cash renting their place while they are away for a few weeks a year to offset their vacation costs, but housing shouldn’t be locked away from a long term resident.
You can audit Debian, or rebuild it yourself. Try that with Windows.