athrun

Cooked unripe jackfruit is a very popular ingredient where I come from, but we typically combine it with smoked pork or chicken. It's very very yummy.

I wouldn't say the texture resembles pulled pork though. Maybe visually if you squint a little.

The main challenge with unripe jackfruit is that it's difficult to cut and prepare without making a mess. There's a sort of extremely sticky glue that comes out of it. It will ruin your kitchen if you're unprepared. It's best to buy it at the market where it has been freshly cut and sliced for you.

Apparently it’s still allowed in Australia for agricultural uses. That might change this year.

https://www.apvma.gov.au/resources/chemicals-news/chlorpyrif...

Ooh. I would never had noticed. And now I can't unsee it!

Looking at the intersection [1], what a badly designed mess it is! You have 2 bike lanes disappearing into the intersection without any sort of protection.

Cars can be parked right up to the ped crossings, potentially obscuring what is happening. Looks like a death trap to me.

At a minimum, raising the crossings so that cars have to slow down, and having no parking zones in front the crossings would improve the situation by a lot.

Humans make mistakes all the time, intersections should be designed to accommodate that.

[1] https://maps.app.goo.gl/KUka4HGt5AsVxFjo7

What are you talking about?

All road users do have different rules for using the road: peds, cycles, scooters, motorcycles, cars, cargo trucks, buses, trams, etc. all have specific rules applying to them.

Don't forget that Australia has EFTPOS and most debit cards are co-branded. The RBA is pushing for transactions to be routed over EFTPOS when possible [1].

And obviously, NPP continues to be rolled out: Osko is now widely available and PayTo [2] will be rolled out throughout 2024.

[1] https://www.rba.gov.au/payments-and-infrastructure/debit-car... [2] https://payto.com.au

apparently the 75% improvement is per core: https://news.ycombinator.com/item?id=38451909

Not disagreeing with your overall point, but symbol collision is still very much an issue with dynamic linking on Linux right?

AFAIK, the gnu dynamic linker doesn't do any namespacing (as opposed to Solaris').

I agree the global experience WeWork provides is really unique.

The question is whether that product would have ever been sustainable—had the company been better managed.

You just have to realise that given enough scale everything turns proprietary anyway.

The difference being whether you are internally maintaining your special snowflake, or else paying for a solution maintained for you by a 3rd party.

I feel the same way.

Python has been my goto language for a long time, but lately I've been noticing that I've been holding off on writing new tools with it because on the back of my mind I have this nagging feeling that making them robust and portable will take too much work—and so I don't even bother getting started.

It's this trap of yes you get to ~99% pretty fast, but the last 1% (packaging/distribution) then take forever.

But I'm still looking for a good alternative... Golang does the job—no question, but it doesn't spark joy for me.

100% agreed.

Car lanes in the city consume a significant public resource (space) and encourage negative externalities (noise, heat, air pollution, etc.). They should absolutely be replaced with more space efficient options: tram tracks & bike lanes.

I think it's important to separate rural and suburbia.

I agree that the sense of community can be high in rural areas. People who live there can be very strongly rooted in the place. Depopulation is taking its toll though.

Suburbia on the other hand...

I agree. They have weird food safety standards!

Especially when it comes to the fermented stuff. Cheese is a good example: most of the good stuff is severely restricted in the US. Idem for cured meat—they mostly don't allow non-pink salt cured meat. Cooking temperatures in restaurant settings are also on the very safe side (finding pink pork is rare for example).

All of this contributes to food that is often underwhelming taste-wise.

> a grocery store chain

Here's your problem right there. There's not a real need for this, when you can just go to your local market.

Whole Foods works in the US because in most places this is the only option to obtain (quality) fresh produce. Not so in France.

It's a fundamentally different approach.

That doesn't make any sense to me.

Most instructions are not atomic, so even if you had runtime checks something like a debugger could still inject invalid state in between your checks, making them ineffective.

If real-time code injection is your threat model, I don't see how runtime checks would get you anywhere.

Exactly. It sounds like currently there's no money to be made supporting old embedded devices (in the consumer space at least), because no one is on the hook for long term maintenance.

Regulations _could_ change the incentives, and create a market for long term servicing. Regulations are hard to get right though...

As an ex-Novell/SUSE employee this makes sense to me. Upstream is supposed to keep marching onwards.

Backporting is _so_ much work. And it's unfortunately not sexy work either, so it's always going to be hard attracting unpaid contributors for it.

If you need stability and long term support as a customer, you have companies like RedHat or SUSE whose entire point is providing 10+ years maintenance on these components.

The tech is still rapidly evolving though—I'm not sure it's realistic to expect standardisation here for a while.

Manufacturers are experimenting with form factors, perf-to-weight ratios, noise levels, weatherproofing, connectivity features, anti-theft mechanisms, ABS, etc.

Battery connectivity and charging is where I'd personally like to see more standardisation—even if there are obvious form factor challenges. Standardisation here could drive costs down, which would benefit the entire market. Maybe the EU should start leaning in this area.

Looks like the OP is still in high school. Kudos to them for pushing through, and having fun with compiler internals.

I wish I had this level of dedication at that age...

AWS will start charging for most IPV4 addresses next year [1]. And I'd expect other cloud providers to follow AWS' lead here.

This could provide the needed push for the Industry to switch.

[1] https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address...

You can export card information to another provider: https://stripe.com/docs/payments/account/data-migrations/pan...

This tool isn’t doing anything particularly complex. It sets up a new pty, attaches the child process to it, listens for OSC52 control codes, and calls pbcopy when appropriate.

You can wrap your ssh session with it and you’re done.

It’s very elegant and multiple orders of magnitude less complex than something like tmux.

Simply wrap your shell with osc52pty to get OSC52 support in Terminal.app

https://github.com/roy2220/osc52pty

Ideally, you want people deeply familiar with the original codebase doing the rewrite.

What usually happens instead is that the rewrite happens because the original code has been handed off to a new set of people. They're not deeply familiar with the code. It's confusing to them. It's not obvious why things have been done in a specific way. And so they decide rewriting it from scratch is the better option.

Unfortunately, they're not in the best position to come up with a solution that incorporates the right lessons from the original design.

It depends on the definition of UNIX, but typically Linux doesn’t count as UNIX.

You can draw a continuous—if very torturous—line between Bell Labs’ UNIX original codebase and modern macOS/iOS.

Not OP, but I found there's a sort of bell curve with Linux support on laptops.

Initially your hardware is likely very new, so some things won't quite work out of the box.

Then, assuming you bought a popular piece of hardware, things get progressively better for you: improved driver support land in the kernel, distros get better at auto-configuring for your hardware, etc.

Finally, 3 years out, upstream development has moved on, your specific hardware configuration is no longer actively tested, and things start to break left and right.

All in all, you have a small window of optimal Linux support for your hardware.

It's challenging to restart a service without dropping connections with xinetd.

Even more so when the process is misbehaving, has children, and is not exiting cleanly.

Europe is a big place, but indeed I'd say in most of EU using SMS to communicate between people is a bit old school. I'd say most people have moved to WhatsApp (or equivalent).

SMS is typically used for notifications-style messaging (or spam), so the impact of this change is probably minimal for a lot of people there. Even chat-bot/support style messaging in the B2C space are moving to WhatsApp (or equivalent).

Is there any content on justine.lol related to her political views? I haven't found any.