skysight-inc/HackerNews huggingface dataset:
As much as I despise FB, the Pages, and Groups, are great.

I do think Nextdoor will give FB competition though. If they don't buy it up?

(I despise Nextdoor. To me it's just people complaining about their neighborhood. Will never understand the guy who sits home, and complains about the car parked on the street, or who's dog deficated on their lawn. That said, I hear strangers taking about the site, and asking for invites. It's privately owned now, but will make a few people billionaires soon.)
The things I had in mind:

1. I sometimes participate in Zoom/Meet calls when walking around SF. Not often enough to have a representative sample, but I know I've had a non-zero number of 1-2 second drops.

2. Students are often on a budget, and may have data caps on their mobile plans. Running out of data towards the end of the month might be OK if you're mostly in your room or the library. But it might impede you from participating in a lecture if you're walking out of wifi range.
"The ideological movement that I favor triggered a rise in crime, so I'm going to minimize that rise in crime by comparing it to overall crime levels several decades ago, after I first denied the rise was occurring in the first place"

https://www.denverpost.com/denver-homicides/ (Murders increased sharply in 2020)
https://www.mprnews.org/story/2021/07/27/violent-crime-surge...
https://dps.mn.gov/divisions/bca/bca-divisions/mnjis/Documen...
https://www.news10.com/news/ny-news/nypd-shootings-up-166-fu... (shootings up 166%, totally not a big deal according to you)

Like I always tell climate deniers, it's not the temperature, it's the rate of change that's the problem. The Earth was far hotter in the time of the dinosaurs, but that doesn't mean it's not a problem that it's getting hotter now. You sound like them, but with crime instead of climate.

And 2019-2020 saw the sharpest increase in murders since the FBI began collecting stats in the 60s according to this article from CNN:
https://www.cnn.com/2021/07/29/us/homicide-rise-us-report/in...

Since the article doesn't support your thesis, feel free to denounce it as right wing propaganda, like you've done elsewhere in this thread. That's totally what CNN and the AP are known for, right?
i am not an audiophile but for classical music, and esp full orchestras very good headphones and flacs are the order of the day. i dont think it's a good idea to to lossy compress classical music...
I was not downvoted, I was flagged and removed.
Don’t use single-factor auth on Internet-exposed systems
I've been using Standard Notes for 2 weeks and it's solid. I like the fairly minimal UI, ability to self-host, and ability to just pay them to run it. Syncs fast.
Q.: How do I stop telemarketers from calling me about car extended warranty?

A.: Have you tried buying a car extended warranty?

P.S.: I don't have a car

P.P.S.: Have you tried buying a car?
Show HN: Open-Source Cloud Security Alert Contextualization
Because the design of async in Rust precludes that. Some of the details are leaky. For example, recursive functions require dynamic allocation in an async context because the async state must be statically sized. See https://rust-lang.github.io/async-book/07_workarounds/04_rec...

There's no easy way to get around the function color problem unless you went the way Go did. But Go's choice made C ABI interoperability more complex. Rust chose simpler C ABI interop, at least for the sync case--no matter which choice you make neither approach makes async interop seamless.

The fun part will be seeing how Rust integrates async and fallible allocation. Both of these issues you could see coming from 10 years away, and also see how they'd interact, but Rust devs decided to punt on some of these hard decisions early on.

This sort of wheel reinvention is what you typically see in every new language, unfortunately, and you typically see them resolved in much the same way because solutions are path dependent on very early design decisions, and almost everybody makes the same early decisions. Except for Go. Go made the decisions it did because the designers had decades of language design experience, including decades of async experience under their belt. Rust designers came with a different set of experiences and goals, and this shows. (Not saying Go is better than Rust--in fact, non-fallible allocations was always a show-stopper for me in some critical niches. But Go made the most difficult decisions up front, and that included putting async first.)
> Why can’t I just click a button and follow all the local events for my favorite artist/venue/team/theater/charity? Why do I still have to manually create events and copy and paste details? Why are there so few “add to calendar” and why do they often fail?

It's because of advertising.

Artists, venues, teams, theaters, charities and other performers may themselves not care - they make money on you being there. But everyone else between you and the event, they make money on your attention. They explicitly don't want you to streamline or automate event discovery and attendance scheduling. They want you to visit their pages, and be exposed to ads (whether it's regular ads where they get paid per click, or ads for different events with which they make money on you deciding to attend).

The "attention economy" is, by definition, built on making everything inefficient and full of hassle. To monetize attention, you have to make the users pay it first.

This may be an tired point, but I feel it bears repeating. The problem isn't one of technology - the tech for what you want exists, and actually worked much better in the past. The problem is businesses: they actively don't want you to use the Internet in this way.
Here's a more recent update: https://abc7ny.com/ny-nursing-home-deaths-kathy-hochul-andre...
Yes, it's not a drop-in replacement. How do we get a drop-in replacement?
My take: as customers we have to pay for incomplete solutions and then be vocal customers. Take my money! This is the way. Otherwise "free" and "open source" solutions will just never reach the level of quality needed to take off.
Show HN: Skybison, an optimized greenfield Python runtime
I think you need a way to be explicit on which override you want to call.

So in addition to the await and the implicit sync:

do_something().await;
do_something();

You also need a way to directly call the sync and async version:

do_something().sync; // I really want the sync version
do_something().async; // I want the Promise result
> It turned out that they [The Guardian] were burnt, and wrote about their painful migration to a RDBMS and to safety

It's not really fair to judge technical decisions retroactively.

PostgreSQL in 2012 wasn't the same as in 2018. PostgreSQL was uncommon back then, there was a limited talent pool, it was painful to operate/failover/scale/shard, and it wasn't yet available on RDS. JSONB support only arrived to Postgres in Dec/2014.

The alternatives (e.g. MySQL) were also problematic, e.g. locking tables every time a new column was added was likely a deal-breaker.

They only migrated to PostgreSQL because they didn't want the pain and downtime of self-hosting MongoDB, but there didn't seem to be any major architectural issues. In this case it seemed like specific issues with MongoDB in production rather than NoSQL in general.

He briefly touches on the downsides during the talk, but the purpose of a talk is to excite and pique somebody's interest.

https://youtu.be/qI_g07C_Q5I?t=3120

In the book he uses more nuanced language and warns that it's not something to be used on every occasion.

* "It’s essential to test your expectations about programmer productivity and/or performance before committing to using a NoSQL technology."

* "Most applications, particularly nonstrategic ones, should stick with relational technology—at
least until the NoSQL ecosystem becomes more mature."

* "But we also realize that there are many cases, indeed the
majority of cases, where you’re better off sticking with the default option of a relational database."

* "There’s no shame in doing the assessments for
programmability and performance, finding no clear advantage, and staying with the relational option."

> I meantioned CQRS, the wider context is microservices.

Regarding microservices, he states that you shouldn't start with complex distributed architecture even if you're confident you'll need it in the future.

https://martinfowler.com/bliki/MonolithFirst.html

> Martin Fowler is dangerous in this regard, there isn't a bandwagon he doesn't jump on making it sound like it is the new normal

While he talked about hyped technologies, I don't think you can blame him for bad decisions other people have made after watching his talks.

> My main point was that we should focus first on learning and applying well ageless fundamentals and mature solutions, rather than on shoehorning the latest fad. Only in extreme cases should that new idea from a FAANG be adopted.

Indeed, nowadays I usually choose boring technology instead of the latest fads

https://mcfunley.com/choose-boring-technology
My secret method to learning a language:

1. Read or listen to something in your target language.
2. Work out the meaning of a word you don't know (using a dictionary, teacher, context clues etc).

Do this 1000 to 10,000 times and you'll have a formidable knowledge of your target language.

Of course, the first thing people do is say: "Aha, I can optimise this! I'll make a list of all the words and just learn that!". Instantly you've removed all context, grammar and likely pronunciation (if the list is written only) from the language. Making an enormous word list is kind of taking the language out of the language.
> “We have a situation today,” Beil says, “in which our smartphone cameras are producing pictures according to the criteria of software designers, who have made a lot of egregious assumptions about the tonality of skin color.”

Making any such assumption, of any quality, is egregious; it has no place in the camera application, other than as some opt-in configuration in the category of special effects.
It sounds like any bad reports you hear come out of China is evidence that China is bad, and any good reports you hear come out of China is evidence that China is lying or has brainwashed its population. That's a pretty flawed epistemology in my opinion.
The upper limit on decent consumer internet is in the 5-10x ratio for oversubscription. 100x is going to be pretty awful, akin to how Xplornet runs there wireless networks (hint: you don't want to be like Xplornet). On my own FTTH network we see somewhere around 3-4 Mbps per subscriber at the 95th percentile currently. 2 years ago it was closer to 2-3 Mbps. COVID made quite a difference when it hit as peak usage ramped up around 10am each day rather than the 5-6pm pre-COVID.

The other downside of how Starlink is building their network is that upload capacity is seriously latency limited for bursts. GPON also uses a shared medium for uplink, and you can "feel" the upload latency at 20km since your node has to tell the other end how much data you need to send before you'll get a grant that lets you send your burst. With all the overhead of modern web pages, the 500 km RTT will feel quite a bit worse than a GPON network at 20 km, and GPON already feels worse than a straight 1 Gbps full duplex ethernet connection. Otoh, Starlink will probably work wonderfully for streaming since it's all bulk data that doesn't care about latency.
Exactly. It is the same mechanism by which trying to stop smoking by reducing the number of cigarretes usually don't work. The "every other hour cigarrete" becomes almost an orgasmic experience.
These people are not having a mature/rational response to a minor inconvenience.
Coding a Text Editor in J [YouTube]
>If you blow a tire, run into a deer, or have a transmission failure while you are cruising down the highway at 80mph you have seconds (at most) to react and respond

When they happen all you do it move over and come to a stop. Unless you go Full Redditor(TM) and start adding a bunch of extreme control inputs none of these things are that bad. They don't require much reaction at all even if you are paralyzed by indecision it can still turn out fine since all you have to do is stop.

Blowouts are a non-event, IMO, just a flat tire with an extra audio alert.

Automatic transmissions basically don't fail in unsafe ways. Worst case you'll find some extra neutrals and make an ass out of yourself failing to merge or something. Splitting the case on a manual (like you might do if you go for 4th and somehow find 2nd, or jump a vehicle and don't mash the clutch before hitting the ground) is surprisingly uneventful from a maintaining control perspective.

Deer suck, mostly because they tend to break a bunch of expensive cosmetic bits.

Having a hood fly up on you is worse than any of the above events because you can't see. Brake failure kinda sucks too, especially with an automatic trans.
I was refering to the white house spokesperson's Jen Psaki's comments a couple of weeks ago.

But yeah, you are right, alongside the databases of a couple "private public partnership" homeland security dept's contractors.

A question for you in regards to the subject of the US security apparatus : is it really still "theories" at this point ? Maybe are we starting to talk semi-founded allegations now, no ?
> and maybe more surprisingly, add/removing virtual functions

I don't have the spec handy but fairly certain that v-table implementation is compiler specific and while it may work it isn't guaranteed. However if you declare the function symbols as dynamic then you can leverage the linker to dynamically resolve the right symbols with the matching opaque data and achieve binary compatibility(assuming you use the same compiler or a compatible compiler ABI and all other caveats around C++ binary compatibility).
How memes could be another Bitcoin.
Also, Lugano convention (if I remember correctly).
AI copyright laundering is going to be a fascinating new legal domain.
Needed to blur the clutter behind me for meetings. Zoom and Google Meets don't support that on Linux. Couldn't find any existing solution that would give me a decent frame-rate for HD resolution without lagging. Wrote this instead.

Relies heavily on GStreamer under the hood for the video processing bits. And mediapipe for the selfie segmentation bit. Obviously need v4l2loopback to emulate a webcam. It's functional, but feedback and contributions are welcome :)
> it may be a higher initial investment

It IS a MASSIVE investment in time and effort to learn something that will appear as an obstacle MONTHS before it becomes second nature. Plus you spend the rest of you natural life fussing with your .emacs file.
Fair. The most (semi-recent) controversial astronaut I can think of right now might be Martin Fowler and his work on event sourcing + CQRS. I don’t know if he writes code or not, but I’ve heard a lot of angst from the people who have adopted those patterns. I made a small system using those ideas built on AWS Event Bus and it generally worked quite well, but I can see where making that pattern the law in a larger setting could be excruciating.
I think some of the technologies he lists are just bad, not over-engineered. Usually "complicated" and "bad" are signs of not doing enough engineering; just shipping what you have and bolting on haphazard extensions as people think of them. XML was that, and so were XML-RPC and SOAP.

You can see this happening with the newer technologies. JSON has a lot of quirks, like not having binary or integer types. So people have bolted those on. JSON doesn't have schema definitions (which are nice if you, say, want to generate code to talk to an API), so we're bolting those on (JSON Schema, OpenAPI, etc.) Admittedly, it's all a lot easier to understand this time around.

To some extent, I'm not sure if we as a field learn from the past, or just reinvent it every 15 years and do a little better accidentally. (Remember the PC revolution, and how you wouldn't have to connect to a big mainframe to do computing? That revolution died and now we carry around $1500 dumb terminals in our pockets, while all the software runs on a mainframe!)
The above is correct - this would take more to cover here but I'd quickly suggest maybe watching something from active developers?

You need to realize that the basic principles were NOT asked for by the major users of GPLv2. When initially discussed way before v3 they were rejected. There was no scoping of need here, certainly not by major projects like Linux.

https://youtu.be/PaKIZ7gJlRU?t=130

(start at beginning if you want more context).

Ubuntu went through this as well, and basically had to get the FSF to (privately) say that they wouldn't enforce the key release process for tivoization against Ubuntu. It was that or use the Microsoft shim.

It was just one sketchy / dicy deal after another. Crazy how wrong GPLv3 was in terms of a natural revision to v2 for developers. I doubt Linux has changed to GPLv3 or will personally, but we will see I guess. Good to see some GPLv2 options here that people can use in devices etc.

And the BSD's and MIT licenses took off as a result, GPL overall lost out as a result of the v3 mess in my view (as a GPLv2 fan that's a bummer).

Yes, the drafting part was "open" in the sense that lawyers got involved and the license got VERY very complex. If that's a win - go for it - most developers just passed on it.
These people have no other way to voice their displeasure so they're predictably using the limited means available to them.

I don't see why this is so baffling. Humans gonna human.
I think people often forget how much time kids actually spend learning their mother tongue. They don’t go to a night class a few times a week, they spend hours each day for several years, both at home and then later at school, before becoming “fluent”. How many adults truly do that, and can’t speak the language afterwards? Brain plasticity is definitely a thing but it’s not as big of a dealbreaker as people often make it out to be.
> dark pattern

Just to get the concept a soft introduction, there are people saying we should switch to the term "coercive design."

The reasons for it are fairly obvious, and I'm dubious about the degree to which some prioritize these things. But overall, "coercive design" is actually pretty descriptive, and I figured it's better coming from me than someone who likely consumes a lot of rage-bait and "dunking" fantasies in their free time.
So don't :). It's not a competition.

"Confusing terminology and lack of conformance with CUA" (aka. being older than both CUA and modern terminology) is perhaps a stumbling block for some, but arguably not that big once a wannabe-user decides to extend their attention span beyond 30 seconds.
I feel AOL failed because of managment period.

I never understood what they did with all those programmers.

I'm not in favor of hiring a CEO just because they kinda looked good on paper. I won't even mention the person's name, and don't blame it all on that person. Amazon was a slow sinking ship.
Why is this still the case? What is the advantage for console manufacturers to have restricted APIs which you need an NDA to access?
I love apple hardware, but despise the software.

I could only live with apple after I have blocked all apple nagware domains at pihole. Life is beautiful now:
* i don't get update notifications, while i am watching a movie on apple tv. ( who thought thats a good idea ?? )
* i don't get nagware on phone to update the phone
* no more "please use icloud" bs

Honestly, whenever i want to update my device i see latest version and reviews. If a bunch of reddit posts show it to be nagware than actual updates, i skip it.

Of course, it needs some work on my part. But if you like apple hardware, this might be a good way.

If you are looking for domains to block, let me know and i can send the full list including some regexes that i use in pihole.
It's tricky, I have had a DSLR for around 8 years now, not the most expensive one but not cheap either and I have a couple of lenses to do damage.

The problem is that my iPhone takes an amazing photo now, in the last couple of years smartphones have built amazing image processing and the ability to take a crystal clear shot without much intervention.

As an example, I went to a desert dirt bike/buggy race a few months ago and I took my DSLR. It allowed me to take some amazing photos at a distance with my 200m lens and they looked fantastic. However for taking photos up close or in motion the iPhone was fantastic. It allowed me to take burst shots of images of fast moving objects, and automatically showed me the best image of that group of burst images and allowed me to delete all others I rejected on the fly.

The only downside is that it takes a serious toll on the iPhone battery, whereas the DSLR chugs through hundreds of photos without blinking an eye (only a shutter).

DSLR's can get you an amazing photo if you have the kit for that type of photo and the settings dialed in. For many of us owning and using a DSLR is a hobby and we enjoy getting the most out of our shots. I think a DSLR will still give you the best image for most shots for now, but smartphones will only keep getting better. And they will allow you to capture most shots with little to not thought.
Billion Laughs Attack
What about software updates? (not forcing you to download, just telling you that one exists) Or update to an app?
"You're holding it wrong" -- Steve Jobs, June 2010
Bad weather is certainly a factor in a lot of General Aviation accidents. VFR into IMC (Visual Flight Rules, ie you fly by looking where you're going; into Instrument Meteorological Conditions, ie you can't see very far due to low cloud or nightfall) kills a bunch of people every year. Some of those killed are IFR rated. In theory they know how to fly a plane when you can't see where you're going, but theory and practice are different.

One thing that's different between GA and driving is that you could stop driving. An hour from home, realising that the road really is too treacherous, you could pull over and walk. Up in the sky they don't have that option at a moment's notice. But one thing that's exactly the same is mission mindset - people fixate on what they intended to do until after it's far too late rather than have contingency plans.
What about fraud alerts?

Eg your bank notifying you that strange activity is happening on your account, or someone is trying to buy a car using your credit?
It does, however, sound like the cyberspace equivalent to the meatspace activity in question.
> Ideally, you want to have a game where so much is going on, that you NEED to split up the tasks to multiple teammates. I don't know, maybe have each of the players doing an "Overcook'd" style minigame, trying to do whatever their sections of the ship need to get done.

Puzzle Pirates really nailed this for me; each ship had a number of action stations (with different kinds of puzzles) that did different tasks, such as providing speed/maneuverability to the ship, pumping the bilge, or keeping the cannons loaded. This all came together in ship-to-ship combat, where having the crew man the stations appropriately was integral to the captain being able to fight other ships... and then boarding was another game.
Calendars. Many people have died on that hill.

I remember when Chandler was supposed to be the last word in calendars. Even Mitch Kapoor of Lotus123 fame got involved (https://www.chandlerproject.org/).

There's something very Bermuda-triangly about Calendar applications. Why is it that in the year 2021 no one has truly cracked the problem yet?
They probably want to keep it out while they vaccinate. They currently are around 20% fully vaccinated and around 40% with at least one shot, and vaccination is proceeding at a decent pace.
Often I already have the file in question open, so it's just :17 to jump to line 17.

If I don't have the file active but it's open (very likely if I have a compile error for it), then I can foreground the buffer with :b myfile<CR>. Then :17 to jump to line 17.

If the file isn't open at all, either fzf (\t myfile) or just :e path/to/myfile.