skysight-inc/HackerNews huggingface dataset:
This comment inflates the upside risk (risk that every developer reinventing the wheel creates lower chance of hack of their code succeeding) and discounts the downside risk (the increased costs associated with elimination of specialization/consolidation of code into reusable libraries).

> Instead, they'll have to tailor an attack for your code base.

This misstates the actual threat.

Assume detection of exploits is automated (even if it isn’t completely automated now). Assume exploit code is modularized and passed around on hacker markets, because they are.

Your recommendation only increases the cost to exploit by a small factor, but it also increases the inevitable costs of legitimate usage by possibly a much larger factor (patching the inevitable bugs which are found). Because developers aren’t specializing (in how to efficiently+safely write logging code) bugs both in the designs phase and implementation phase will be higher than in a counterfactual specialization world.
Seconded - it's fabulous to find that not only is he writing, but writing posts with titles like:

http://www.charlespetzold.com/blog/2021/08/Screw-You-Microso...

no M$-lapdog, he. I learnt my Win16 from the first edition of "Programming Windows" and would have learnt my modern UI from the newest edition if MS hadn't been so busy throwing the bathwater out with the Windows Phone baby that I lost heart.
To explain a mystery is to tell a story. A story about a thing that joins up nicely with our stories about everything else.

The story is important. More important than the actual thing maybe.

I think it's so important because the story can be kept and carried around, like money. And it can be communicated. Translated into the noosphere or whatever. And everybody likes the noosphere.
Yes because Microsoft got a special license from Apple that allows for the virtualization of Mac OS on non Apple hardware...

The rest of us is still running on racks of Mac Minis
Funny you use the word "disrupt" in your ending paragraph, given the HN community is so full of aspirational start up founders and engineers who prided themselves on being "disrupters" at least that was the rallying call for a decade. You can read what Peter Thiel or Marc Andressen have to say about academic findings and you can see that attitude re: academia has basically propagated down.

Ultimately, a lot of people are scoring points online calling academic research bunk because a lot of it is bunk, published for professional gain instead of pushing human knowledge further which is the entire supposed reason for the author's grant and their institution even existing. I singled out social science cause engineers/hard scientists always have thumbed their nose at social scientists, sometimes for very good reasons (they hijack the language and techniques of hard science to give themselves credibility even when its not appropriate) and sometimes for not good reasons (they can't code as well as me so they are invalid).
Dave Clark left to become CEO of Flexport. Maybe the retail conditions influenced this decision, but CEO of Flexport seems like an obvious fit for him.
I sure hope that the steel in skyscrapers and stuff is going to last a long freaking time though.
Installing Rooftop Solar Can Be a Breeze. Just Look at Australia
The append pattern also implies the opposite of reality, in that it also (usually!) mutates mySlice. Which is the source of one of the two(?) possible races in that piece of code.
The immoral design of Diablo Immortal
Haha, I guess crossing the enterprise chasm is a challenge for enterprise chasm crossing enabling companies as well.

Is DDoS and replay protection built into the SSO product? Or does that need to be handled by customers?
Related thread:
https://news.ycombinator.com/item?id=31692543

This is the followup article heavily discussed in that thread.
I've got all but 1 job in my career through talking to recruiters on LinkedIn.

Once you find a couple of good ones and make sure to have a coffee or something with them from time to time, you can get a really good feel for what's out there and where you should be aiming your efforts.
I’ve been a pro photographer/producer for over 30 years. I specialize in unique, hard to find subjects and have even designed and built my own camera systems to accomplish my goals. I have genuinely loved this work. Like pinch myself “I can’t believe I’m being paid to travel into the wilds of Borneo” type excitement.

I come from a family of laborers, riddled with addiction, poverty and death. I’m a weird outlier.

Yes I worked hard. In fact I put on blinders and made absolutely everything about my work. But I have to acknowledge luck.

I’ve seen so many smart, determined, hard working people get crushed by this business. I’m so suspicious of any self help type advice about following your dream to do what you love. I don’t want to be discouraging and kind of admire how young people propel their ambition because lack of experience is actually helpful.

I was kind of dumb to start in this field. But what did I have to lose? But damn if i didn’t get lucky.

No regrets here. But some guilt about the giant unfairness of it all.
> It is still a task many developers aren't able to do.

Yeah, I think parallelism is naturally intimidating to many developers used to single-threaded work.

I just those developers encounter Rust.
Yea I honestly don’t understand why many devs use a mac to develop software for linux. Sure if you are developing native OSX or iOS software it makes sense, but why torment yourself otherwise?

The main pain point with running linux on a laptop is finding a suitable pairing of the hardware and software so that everything works (device driver support, no bios/uefi/acpi bugs, etc).

Finding some good hardware to run linux only has to be done once maybe every 3-4 years and them you can just carbon copy the setup for all of your devs.

Heck, I will save you some work: the dell XPS 13 works great with the latest stable release of Ubuntu.
Serious project, the name is mocking Web3.
1. Could have solve energy 50 years ago. Thanks Greenpeace

2. Let's all buy a $70,000 electric car. The insurance rate alone would negate any gas savings across a 40 year time frame for most people
Cap Theorem – Two decades and few clouds later (2021) [pdf]
Presentation: https://youtu.be/K3Ahfbn7tPk
That's a funny spoof for a GUI. I don't know what design language was used here, but it's pretty outdated by now.

Windows (for domain admins) has similar tools to OpenSSL. How do you use that, you may ask? Simple: wizards. There's a wizard to create a CA. There's a wizard to create a CSR. There's a wizard to sign said CSR. There are probably wizards to set up custom wizards.

When you turn OpenSSL into a step-by-step process (with the subcommand chosen by the button that spawns the wizard, as well as a separate wizard for the "mini CA") it becomes quite manageable. Just stuff each part into a separate page and filter out any options that might be irrelevant based on earlier choices.

You'd end up with a seven to eight step wizard for most operations and I doubt you'd be as confused. OpenSSL is forty tools in one executable.
Comparatively unhealthy. Smartphone screens are essentially shining a torch in your face; hardware e-readers are designed for one purpose only and that includes having a screen that does not tax your eyes - apps are no substitute for them.
It wouldn't have been confusing if not for them changing the subject and move the goalposts from their original statement, where the use of "objective" was absolutely material to their meaning, which was that the act is unquestionably immoral:

>> You decide the truth value of something and based on that you further decide that a topic is off limits

> I would normally agree with this viewpoint, but there are things which have an objective quality of being immoral. Supporting the persecution of a group of people because of their ethnicity (or whichever other criteria) is such a thing. Please tell me how I'm wrong about that.
GUI's can be counter productive for theses kind of tool. There are some contexts like "SSL" were the user needs to understand the underlaying concepts a UI cannot teach in itself
That is one of the ruses being perpetuated by disinformation.

https://www.ibj.com/articles/karen-celestino-horseman-conven...
All these dimension reduction methods are extremely similar. The math essentially just preserves nearest neighbors, with a setting for how 'tight' you want the clusters to be.

Check out this image [1] and accompanying paper [2] for further reference

[1] https://www.semanticscholar.org/paper/A-Unifying-Perspective...

[2] https://arxiv.org/abs/2007.08902
The holy grail of a Web SDK
The commenter explained why. (they mentioned the iPhone specifically; this may be the case moreso on there, I don’t follow Android)

It’s because there is a metric shitton of software that goes into the camera app itself, and access to the camera’s hardware does absolutely nothing to enable these features.

IIRC there’s actually some sort of crazy ML shit behind Apple’s native camera app; I would be very curious to see what a raw photo from the same sensor would look like in comparison.

Having said that whatsoever validates the commenter’s point.
I am happy to see them succeeding and expanding into new areas. They have done so much for the tech scene.

At least a few things they did were in use at nearly every job I've ever had, and they did well every time, aside from a few times when a Pi would have been more appropriate.
Everything you listed are at the very end of the list of things that matter to modern day Journalist. If they even make the list.

But reading your comment does sort of put a smile on my face though. The what others would called a non-cynical world view.
> The benefits of a diverse student body, not curing past harms, are key to the test.

That reasoning is just cover for doing what the judges want. They'd never allow racial covenants to return if it were shown whites benefit from living in mostly-white neighborhoods.
Produce Available in the US During Different Months of the Year
> Showing all possible options in a window really isn’t helpful at all.

Well, then you shouldn't.

Almost anything that's mature, evolved and complex can be represented like a nightmare with a bad UI. ffmpeg is the usual extreme example of a bonkers out-of-control parody of itself, yet there are useable UI's that wrap the most essential functionality of ffmpeg by taking some very popular use-cases and making them straightforward. Same thing with git.

I think something similar could be done with OpenSSL. Does everyone who works with OpenSSL really keep all that stuff (like in the OP's article) in their head? Maybe some, but the vast majority of folks will just follow a pattern of usage that someone else "pioneered". No one has time for that kind of incidental complexity, not in a CLI, not in a GUI.
Please submit this as a real letter to the editor to the Economist. They are quite likely to publish it (the last 1 or 2 letters are usually humorous).
Notice shareholders comes before customers
> I never would've guessed that in 2022, Java would start looking more and more appealing in new ways.

I don't quite understand the hatred (to the point of shouting "using Java? Over my dead body), especially in startups, towards Java. I mean, it's a language, big deal. Java's ecosystem more than enough offsets whatever inefficiencies in the language itself, at least for building many of the internal CRUD services. Besides, people like Martin Thompson shows us how to build low-latency applications with ease too. Libraries like JCTools beat the shit out of many new languages when it comes to concurrency for productivity, performance, and reliability. How many engineers in startups claim that they hate Elasticsearch because "Java sucks"? Yet how many can really build a platform as versatile as ES or a Lucene replacement with economical advantages? How many people in startups openly despise Spark or Flink and set out to build a replace because "Java is slow and ugly". Yeah, I've seen a few. And a payment company insists that Rust is the best language because "GC is inefficient and ugly", even though they are still in the phase of product iteration and all their services simply wrap around payment gateways? What's the point?

Disclaimer: I use Go in work. It's not like I have skin in the game for speaking about Java.
This definitely matches my experience using Go at my previous organization.

1. Closures and concurrency really don't mix well. The loop variable capture in particular is very pernicious. There's an open issue to change this behavior in the language: https://github.com/golang/go/issues/20733.

2. Yep. I've seen this problem in our codebase. I've grown to just be very deliberate with data that needs to be shared. Put it all in a struct that's passed around by its pointer.

3. This issue is caught fairly easily by the race detector. Using a sync.Map or a lock around a map is pretty easy to communicate with other Go devs.

4. This should be documented better, but the convention around structs that should not be passed around by value is to embed a noCopy field inside. https://github.com/golang/go/issues/8005#issuecomment-190753...
This will get caught by go vet, since it'll treat it like a Locker.

5 & 6. Go makes it pretty easy to do ad-hoc concurrency as you see fit. This makes it possible for people to just create channels, waitgroups, and goroutines willy-nilly. It's really important to design upfront how you're gonna do an operation concurrently, especially because there aren't many guardrails. I'd suggest that many newcomers stick with x/sync.ErrGroup (which forces you to use its Go method, and can now set a cap on the # of goroutines), and use a *sync.Mutex inside a struct in 99% of cases.

7. Didn't encounter this that often, but sharing a bunch of state between (sub)tests should already be a red flag. Either there's something global that you initialized at the very beginning (like opening a connection), or that state should be scoped and passed down to that individual test, so it can't really infect everything around it.
The path to your next Open Source contribution
I don't like using Apple computers, and don't have an M1, but I've been having similar fun with a Microsoft Surface Pro X (running insiders build of Windows 11 which has x86-64 emulation for NT processes, and runs Android applications, but doesn't support emulation in WSL2). Overall much the same experience with things assuming the only execution environment is inside an x86 docker container. I also found that the "stock stack" Haskell development toolchain install (in WSL2) won't work, again due to lack of build runners at GitHub. Eventually I was able to find workarounds for all the annoyances, mostly involving building components myself.
Can you share one explicit example that is still there today? IIRC the things from that thread were all solved.
> There is a big difference in testing whether something is needed in the near future or you simply stick to your guns and blindly dictate how you believe the future will look like.

There are innumerable successful examples of committing blindly toward a future few people believe in. These are often cases where the objective evidence of success is very limited. If the objective evidence existed then "everyone would be doing it".

This is the crux of my disagreement. Of course we'll both agree that applying the wrong/stupid abstraction is wrong. But that's not what I'm discussing.

I'm talking about this quote specifically:

> Don't look into the future. Because you cannot. And you are both naive and arrogant if you believe you can. Deal with what is known now!

Perhaps you need to reframe this point to make it more clear?

> Don't look into the future. Because you cannot.

This is silly for all the aforementioned reasons. Especially when innovating in tech!

> And you are both naive and arrogant if you believe you can.

Calling someone arrogant for attempting to predict the future in technology. Come on, man.

> Deal with what is known now!

What is known now is what everyone else knows now. Unless you're dealing with the _extremely_ rare case where you have access to information no one else does, innovation requires one to commit to the unknown.
So he’s getting paid full salary for two years and doing nothing? Sounds like a dream!
Clearly "did not read the article" applies to some internet commentators.

The article is pretty good and shows good understanding of what the attack is.
Practice and study should count for naught, school entrance should be based only on genes?
What good is Apple's say if they're not going to provide anything worth using? With that justification, they might as well stop updating Safari at all.
IDE as a Platform
I don’t know that I really count since I’m quite frugal. On my end I think the term mortgages are great since I believe it leads to lower overall interest rates. There’s a lot less risk that gets baked into the price that would be needed for longer terms. I know I’ve compared to other jurisdictions where interest seems way higher.

So it doesn’t cause me any anxiety.
The lesson I'm taking away from this is if the U.S. wanted to support its increasing senior population and improve the loneliness epidemic [1] _and_ obesity epidemic, buying up malls and retrofitting them into public community spaces would be a huge step in the right direction.

[1] https://sitn.hms.harvard.edu/flash/2018/loneliness-an-epidem...
> We'll be multiarch for many years to come.

I think we're entering a long period of multiarch for the "traditional" server/desktop. I expect a lot of good to come out of this on the compiling side (easier to target any OS-arch), and (perhaps more importantly) on the general cross-platform front.
I'm no fan of go, although I think it's better than many other languages for services, but the argument here is against the label "append", not the operation. It's a poor name for the operation, but the documentation is quite clear about what's going on. I'd argue that understanding the keywords and builtins of a language is the bare minimum an engineer should do before he starts writing anything in it.
Google Maps is one such example. Every time you click on something, change the zoom, toggle the layers, etc., it gets saved to state (and persisted to the URL). That way you can use your browser back/forward buttons to switch between different places or views of places, and also share that with your friends.

Miro (the collaborative whiteboard)/Figjam is another... the boards can grow pretty big in x-y space, and losing your place in space is very easy to do, especially if you ctrl-z a few times and forget what you were even working on. Just knowing that "somewhere on this board, something changed" isn't helpful if you can't see what it was.

Analytics is another such use case, for when you're composing queries or search filters, date ranges, etc. Google Analytics does something similar by giving each set of criteria its own unique URL, so that you can use the back/forward in your browser to go between states. Not exactly the same as an undo/redo button, but pretty much the same idea.

Another example: I work for a solar company, and we're building a web app that equipment installers can use to monitor the performance of rooftop solar arrays they've installed. It tracks, for example, each solar module's power production on a heatmap, arranged in the same layout as on the actual roof. There's a lot of interaction that can happen... selecting a particular unit, choosing a particular timeframe, deciding which metric you want to look at, search terms, table filters, sort order, etc.

None of that needs to be written to our database as actual changes to the layout and device pairings. But it would still be handy handy for users to be able to undo/redo, bookmark, permalink, etc.

I think of it this way: A set of UI states like that, taken as a whole, is in and of itself a form of "data"... it is a human user's carefully framed view of some point in time, and some selection of data, that they have deemed important. Being able to save and retrieve that state in case they make a mistake (cat jumped on the mouse) or want to share it with others ("hey, check out what's happening to this module on X date at 4pm") is helpful, even if it doesn't ever need to be written to the server (since it can be stored as local state and/or URL strings).
It is, but I've never seen anyone get banned for using it.
I think you and I are generally on the same page, but we're reading this statement by the root commenter very differently:

> Don't look into the future. Because you cannot. And you are both naive and arrogant if you believe you can. Deal with what is known now!

See my additional response to him elsewhere in the thread where I tried to break it down sentence by sentence.

Everything you're saying is on point for good system design IMO. What he was saying was totally different and IMO is a "dangerous" way of thinking when innovation is important.
Checked my street here in South Australia and 30% of houses have solar (I thought it would be higher). Google Maps says the imagery is from 2022, though it shows a car in the driveway we sold at least a year ago.

It seems very common for industrial properties where a lot of the power usage is daytime - supermarkets and so on are carpeted with solar panels. The systems typically pay for themselves in 3-5 years.
That's Jack Dorsey for you. He has a knack for making things look cool to his target audience.
The Techcrunch article is well written and I thought summarises this rather well.

The headline is pretty reasonable too. Apple can't patch this, and as other commentators point out subsequent attack techniques are only going to make this flaw worse.
You were correct. Geforce Now feels like a generation ahead of Stadia oh my god.
No doubt, but that's not what's brought her down.
it has taken us 2 years to give 60% of the planet a $5 shot despite having 2x world population of shots available.

"capability" should not be confused with "universal accessibility"

and "some people one hundred years ago did horrible things" is a fictional strawman. There are real and present reasons why practically eugenics will lead to stratified and unjust conditions for humanity in practice.
Do you have a source for this claim? As far as I’m aware Azure racks mac minis and has no special license, but I’d be fascinated to be wrong.
The greenest place for humans to live is in dense cities. https://twitter.com/hausfath/status/1418581766047105025
I'm inquiring about actual implementation not Markdown. Markdown -> AST -> CodeMirror vs Markdown -> AST -> ProseMirror.
Oh, it knows. As it won't even run on my Quadra 840AV. :-)
Against what are these efficacy comparisons? Omicron? Other variant?

I have not paid attention to COVID-19 recently and I recall that Chinese vaccines were problematic against Omicron.

If it is so efficient then why the hell they have this security theater in China?
"Simplicity of the Windows architecture"? I wish I had read his book, because I read many other bad books and Win32 always felt so complicated.
I want to know if the idea of the website is clear or not ? and also if the idea is good or not too ?
but it's not at all like that because we're not AIs, chimps didn't hold any monopoly of force over us, and we're embodied beings. If we had evolved into talking Futurama heads we would indeed have a hard time against our chimp competitors regardless of our intellect. You throw Eliezer Yudkowsky into a cage with a chimp and my money is on the ape.