Jochim

This is how you end up with extremists.

The Uber example is also an outright lie.

They acquired those customers by burning billions of dollars to deliver rides below the cost of providing them.

Then they raised prices beyond their competition to account for their ridiculous overheads.

I agree! Your system is already heavily compromised if this is a problem for you.

I think the real problem lies in a lack of visibility into the state of the device. A compromised dongle could easily be transferred between machines. What we need is to make obvious what the machine/device is doing.

Related:

Undocumented backdoor found in Bluetooth chip used by a billion devices

https://news.ycombinator.com/item?id=43301369

I literally described my experience of booking a taxi before Uber. Many of the local services also had apps that showed the location of the car and a fixed price before Uber was available here.

I don't agree that Uber was a better solution than taxis.

They drove their competition out by offering rides far below the cost to provide them.

Now they're more expensive than what they replaced, and with far worse service.

Take pre-booking a car for an early flight for example. Taxi companies would ensure they had someone on shift ahead of time and refuse the booking if they couldn't accommodate you. Uber will accept your booking but leave you to hope that, around the time of your booking, someone decides to open the app and accept it.

It doesnt sound like it's obvious to the driver that it's a pre-booking either. So you'll often see drivers show up 15-20 minutes early, irate that you're not ready to leave.

The worst thing about Uber is that their price distortion seriously damaged their competition, who could not afford to burn tens billions of dollars on the service the business is meant to be making money from.

The US will happily execute someone who could very well be innocent.

Robert Robertson is currently alive on a technicality[0].

[0] https://www.nbcnews.com/news/us-news/texas-set-execute-rober...

Foreign bank account that isn't part of the scheme.

Virtually all of the built in commandlets have one or more aliases set by default.

e.g. Get-ChildItem is aliased to "gci", "ls", and probably "dir" as well.

The main issue with ARC seems to be driver support in specific games, DX11 being particularly problematic.

Intel basically have to catch up on the ~10-20 years of kludges that AMD, Nvidia, and game devs had already implemented when the games were released.

They've been making strong improvements to their drivers though.

Their iGPU is great for home media servers. Low power draw, QuickSync can handle multiple 4k transcodes, and one less part to buy.

iGPUs still aren't a great choice for gaming on desktops, even the latest AMD APUs perform poorly in comparison to the cheaper dGPUs.

Everyone involved does a pretty poor job imo.

The processors/chipsets seem to do what they're they're supposed to. However, it's far too easy for other parties to create a scenario that prevents the system from reaching deeper c-states.

Motherboards manufacturers produce boards that can't go below C3, despite showing up to C10 in the bios. The actual level of support won't ever be mentioned.

PCI devices, e.g. wifi cards, can prevent the system from reaching deeper C states entirely.

Putting devices into a PCI slot connected to the CPU lanes rather than the PCH can also prevent the system reaching the desired states. The CPU slot will frequently be the only choice.

Operating system defaults often prevent the system from reaching deeper c-states. Linux has been worse for this than Microsoft in my experience.

4/5 might mean they're being more adventurous with their food. This won't necessarily suit everybody.

What do you think happens to the wealthy when the government does not ensure the majority of people are well fed and secure?

Does the mob respect property rights?

Honestly, I don't. First, perhaps it's small minded but I don't really feel responsible for every human on the planet, or even a significant percentage.

Do you expect them to respect your right to have those things? IMO, your line of thought leads to violent revolution.

Gitlab's biggest issue has always been their ridiculous approach to pricing. It simply isn't worth paying ~20-30x more per developer than comparable tools.

Feature segmentation can be entirely reasonable. However, gating something like "linking epics"[0] behind what used to be $99/month/user (now POA) is pure hubris.

[0] https://docs.gitlab.com/ee/user/group/epics/linked_epics.htm...

They're not really designing the item though. They're paying a drop-shipping manufacturer to print/etch a graphic or text into a white-label item.

It's so little effort that the platform has been entirely flooded with low quality garbage.

It wasn't really a landslide though.

The winners only received ~1.5٪ more votes than their previous "disastrous" result.

The gains were largely due to the incumbent Tory votes being split by Reform, an extremely anti-immigration populist party.

as an outsider, UK housing prices outside of London are actually quite affordable.

Much like Arkansas/Mississipi, both opportunity and salary are much lower than high CoL areas like London/California.

Both rent and house prices in the UK have far outstripped our comparable neighbours and are causing real issues for people.

New build housing is energy efficient but of poor quality and extremely expensive, often furnished with unusably small rooms.

Not OP but the "-Object" commands are pretty fundamental to creating useful pipelines:

Select-Object - Pick out specific fields from an object, create calculated fields etc.

Where-Object - Drop non-matching objects from the rest of the pipeline.

Group-Object - Cluster objects into groups based on a shared property value.

Sort-Object - Order an array of objects based on a property value.

Get-Content - Read from a file.

ConvertFrom-(CSV/JSON) - Parse a json/csv formatted string into a powershell object.

ConvertTo-(CSV/JSON) - Serialise a powershell object into a csv/json string.

(Parallel)ForEach-Object - Loop over each item in the pipeline, performing one or more actions on it. Usually occurs at the end of the pipeline, or when you need to call an executable that can't handle pipeline input.

One thing I struggled with in the beginning, was not knowing what properties an object might have. You can pipe any object into `Get-Member` and it'll list its available properties and methods.

Many of the "-Object" commands support the use of script blocks if you need to carry out more complex filtering/projection.

This is peak HN: getting accused of being "disingenuous" for making a glib comment complaining about too many "fixed typo" and other trivial commits in a git log.

Making snarky comments isn't particularly interesting, nor does it offer much opportunity for discussing the actual benefits/drawbacks of the topic.

Squashing is great IMO, but the problem is that many organizations prohibit it, because it erases a developer's commit history, because apparently it's really, really interesting to pore through dozens of commits where a developer fixed some whitespace, fixed some typos, etc. (Before you say something about rebasing, these same organizations also frequently prohibit that too.)

That's an issue with the policies of those specific organisations rather than with the idea of generating a changelog from commit messages.

Squashing/Rebasing isn't necessary to generate a clean changelog. You don't need to include every commit by default.

Sadly, we didn't end up implementing it ourselves. Release notes were a "nice to have" so it became one of those things that gets kicked down the road.

The primary advantage of the ticket-based approach is that it's much easier to involve non-dev stakeholders. I'd choose it whenever other people might want input in the process. Most ticketing systems also offer a lot of flexibility, you could incorporate the ticket name, group tickets by relation, block completion states, act on deployments, etc. The ability to edit the note without rebasing is a major bonus as well.

The git-based approach potentially leads to a more readable commit history, and strongly associates any release notes with the actual code change. On the other hand, it's a pain to edit and can distract devs while they're problem solving if not setup well.

I've seen the same thing done within the ticketing system. It's useful when you might want non-developers to contribute to the notes.

Being able to dedicate a tag, field, or work item type is pretty handy.

I think it serves a few potential purposes:

It provides a solid, accurate draft that can be expanded on when targeting non-technical users.

I've often found that lack of visibility leads to messy commits. Surfacing these messages in the changelog introduces an incentive to take more care.

With regards to the usefulness of the descriptions, the associated issue is often linked along with the commit message. This is often omitted in hand-written changelogs. In this case the auto-generated changelog acts as an index, allowing the reader to quickly parse what changed and jump to the associated code or ticket.

This feels like a fairly disingenuous interpretation of how this gets implemented.

Normally, commits must match a particular pattern to be included. Those that start with "feat:" might appear in the features section, while those starting with "bug:" show up in fixes.

A few simple rules are enough to ensure that an intelligible changelog is generated. Minimal cleanup can then focus on making it presentable.

You could even set up your pull request rules to handle this for you. On approval it could look at the linked issue and include the title and appropriate pattern for that issue as the message for any merge/squash commits it creates.

Nationwide actually publish data about the monthly mortgage payment to take home pay ratios of first time buyers[0]. Compared to Q1 2014, repayments accounted for a lower proportion from when their data begins, in Q1 1983, until Q3 1988. Repayments remained higher until Q4 1990.

In 1989 interest rates were at record highs and mortgage interest relief was still a thing. Despite interest rates hovering between 8-12% for the rest of the 1980s, mortgage repayments were consistently a much lower proportion of income.

In 2024 there's no interest relief and we're exiting a period of record low rates. The rise to 5.25% already puts us in a worse position than when rates were at 10%, 14.5% would disastrous.

[0] https://www.nationwidehousepriceindex.co.uk/charts

Interest rates get brought up every time this topic is discussed and the math remains the same. Even accounting for the difference in interest rates, people are much worse off today than they were in the 80s.

Funny how often that seems to happen with the IDF.

The torrents would be snapshots of the repo at a particular point in time. Updates couldn't be fetched through the torrent via git pull.

I'd assume that op wants a torrent that can be pushed/pulled from.

BT customer service are just as hopeless at dealing with OpenReach as everyone else.

I spent three months trying to get them to switch my line over to fibre after OpenReach had stated it was available. Their approach was to hope that waiting long enough would fix the problem.

Eventually someone just closed my existing line and immediately opened a new one.

Interestingly Chinese app's algorithm chooses more STEM videos, while Western version just pushes addictive crap.

That's simply a lie. Douyin is full of the same trash as Tiktok.

fwiw this seems to be partially in place already.

Requests for access to files, location, mic, and camera usually give me the option of allowing them all of the time or only when the app is open.

I've also noticed system notifications stating that permissions will be used from unused apps.

Greater configurability is always nice though.