JusticeJuice

It's the original end to end testing!

Loom does also have a trim and edit after recording feature, I use it all the time

Dead link

If an artist has full control of their IP, yes they can just take their music down.

Dissatisfaction with the payout is only one aspect of why some artists are leaving Spotify. I personally find it super weird how much Spotify profit is getting funnelled into arm manufacturing. Like why should listening to music help new AI drone tech to get developed? Tf?

Interesting talk. I think it's just a matter of making tooling where it's so easy, cheap, and simple enough that doing realtime doesn't introduce any extra time cost to a business compared to CRUD.

That's a really cool project! The realtime message aspect reminds me a bit of https://honk.me/, but for like, docs.

I remember being literally 12 when google docs was launched, which featured real-time sync, and a collaborative cursor. I remember thinking that this is how all web experience will be in the future, at the time 'cloud computing' was the buzzword - I (incorrectly) thought realtime collaboration was the very definition of cloud computing.

And then it just... never happened. 20 years went by, and most web products are still CRUD experiences, such as this site included.

The funny thing is it feels like it's been on the verge of becoming mainstream for all this time. When meteor.js got popular I was really excited, and then with react surely it was gonna happen - but even now, it's still not the default choice for new software.

I'm still really excited to see it happen, and I do think it will happen eventually - it's just trickier than it looks, and it's tricky to make the tooling so cheap that it's worth it in all situations.

I wanted to learn a bit about backend development, so I've been building my own version of soundcloud with supabase. Main thing I've learnt so far, auth is flipping complicated. But it's been really fun! The audio compression is done clientside with ffmpeg and WASM, I'm pretty pleased with that approach. Everything is pretty busted atm, but I'm trying to get to a 'walking skeleton' then polish. I've been devlogging the process as I go for fun.

https://cassette.world/

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

Their finding of LLMs working best at simple tasks, LRMs working best at medium complexity tasks, and then neither succeeding at actually complex tasks is good to know.

I know that aws has a few reliability engineers in Wellington, but that’s just to support their aus servers. There really isn’t that many foreign companies outsourcing support to NZ.

I worked in the nz tech startup market for 8 years before moving overseas. To say nz tech is a tiny market is an understatement, when the population of the country is the size of most cities, there’s just that not that many opportunities.

It does mean for many people the only way for career growth is to go elsewhere. When I left nz my salary 3x’d.

The opportunity here is that there is many talented tech workers who choose to stay in NZ for lifestyle reasons. Foreign companies can compete so easily on salaries, it’s easy to just buy the top of the market for half the price. You will need local recruitment help though to find them.

The time zones are rough, you need to be a company that’s embraced async working, and are able to give a team a clear brief and just let them do it. But the hiring opportunities are there.

lol sus

That’s exactly what the library does for its web renderer. There’s a svg renderer and a web renderer.

I'd love to know what individual piece has moved the furthest from it's starting point.

The key thing to understand about typeface copyright is you can copyright the font file, but not the actual shape of the font (as that video you linked covers).

So say as you said, you had access to a font, you used it in a logo. Then you lost access. It's fine to keep using the logo, any assets you've created while you had access you can keep using. What you can't do is keep using that font file on your machine to start making making new assets. This is why for graphic design fonts are often licensed based on the number of machines they're installed on.

For web, it's often a subscription for a certain number of page views. If you no longer pay the subscription, then you're no longer allowed to serve the font file. Enforcing this however, is really tricky for foundries as you'd expect.

For app use, the license don't account for 'page views' as they figure it's impossible to track (and for the foundry to check). That's often why the figure is more for native apps. They're also kinda taking a guess that companies making apps pay more.

This is why a lot of big businesses will just outright 'buy' a font, so they have access forever with no limitations. If you're committing to a particular font for your brand, it often makes sense to just drop the cash and get it. It's also why so many really big companies just make or commission their own typefaces - it can be cheaper than trying to find some deal with a foundry. A good typeface will take one person about 2-3 years to make, but if you have 1k employees.... no biggie.

It's worth noting most serious foundries don't focus on 'small' customers - they're targeting very large businesses. The pricing doesn't scale down to most normal people, unfortunately - however if they did they'd be dramatically reducing income from the 'whales'. There's also undeniably a bit of price-value bias.

This all varies a bit foundry to foundry, but that's the most common setups and why.

He's not saying americans couldn't learn to do it. He's saying there aren't many people in the US to hire who already know how to do it.

> Do you mean that front-ends have proprietary code?

Yes, sorry for not being clear, but this is what I meant. When the average person uses crypto, they're not using an open source app to buy/sell it. They'll be doing it through a propriety service, with a non-open source front-end. That service will build on top of a lot of great open source tech yes, but the final layer is very likely a private company.

I know there are open source options, but my understanding is the overwhelming majority of human trades won't be using them. My point is, refusing to use pix because there's not an open source mobile app is odd to me.

Sorry, I should've been way more clear. But this is what I was getting at. If the average person wants to buy or trade in crypto, they don't reach for an open source solution, they'll use a proprietary service. I know that's built ontop of a lot of great open source tech, but the final 'app' people interact with isn't open. The fact that pix doesn't have an open source app just strikes me as a weird reason not to use it.

> Something as common as the dominant payment system should not depend on proprietary software.

Name one dominant payment system worldwide that doesn't? Banks are proprietary, credit cards are proprietary, paypal, crypto is all proprietary.

Consider https://www.framer.com/

This is so cool.

It's really really hard to 'aim' a 6km deep hole. Hitting a slab of tough rock can deflect the drillbit off course. If you remember the Chilean miner rescue in 2010, who got rescued by a new hole being drilled - they had 3 seperate holes being drilled at the same time as backups, just because they were worried about the success rate of actually hitting their target. And that was only 0.7km underground.

You'd be surprised. I know a few people who couldn't really code before LLMs, but now with LLMs they can just brute-force through problems. They seem pretty undetered about 'trusting' the solution, if they ran it and it worked for them, it gets shipped.

+1

Also, this collection spans much more time than communist Vietnam? 1900-2020s? Weird take.

Oh 100%, the content (and context) is completely different. The similarity I mean is a government passing a law that asks a foreign company to hand data over to them.

Yeah totally, it only works due to their influence. The uk has nothing to backup these demands.

There are tangentially similar precedents already, such as the American FACTA law. It is obviously a quite different context, as it just relates to financial information, not all information - but it's a law from the US government, that demands foreign companies send information back to the US.

The wild thing is that foreign companies actually do it. To avoid annoying the US, a lot of other governments ensure that the data is reported.

https://en.wikipedia.org/wiki/Foreign_Account_Tax_Compliance...

I just looked up your app out of curiosity, and realized I had just watched your video about react's inverted-reactivity model just a few hours ago! Small world!

> All IT workers are exempted from mobilization.

This isn't entirely true. A friend of mine (who works in IT) got drafted. In 3 days he ended up getting a pregnancy certificate faked, so he and his girlfriend could get legally married quickly (for immigration options elsewhere) - and fled the country.

The draft is unequal, they are concerned about their IT worker shortage. The majority of drafting is happening in impoverished areas of the country, and ethnic minorities. Often people think they'll just be doing a driving job or something, and end up in combat. But nobody is truly safe. Your friend is taking a large gamble by visiting.

Bonus bug report, underscores in filenames seem to mess with things. E.g. DCS_0035 and DCS_0036 both resolve to DCS_(1), overwriting each other.