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?
Spotify's profit is not being funneled into arms manufacturing though, only by stretching that the money Daniel Ek made by being the founder of Spotify is "Spotify's profits" which he then used to make an investment into Helsing. Even though Spotify wasn't profitable at all for most of the almost ~20 years of existence.
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.
Real-time collaboration ?
Discord (not fundamentally different than IRC, which has been around since the 90s),
Zoom (or any other teleconferencing software)
This site being a CRUD app is a feature. Sometimes simplicity is best. I wouldn't want realtime updates, too distracting.
I feel the same way. The initial magic of real-timeness felt like a glimpse into a future that... where is it?
I'm still excited about the prospects of it — shameless plug: actually building a tool with one-of-a-kind messaging experience that's truly real-time in the Google docs collaboration way (no compose box, no send button): https://kraa.io/hackernews
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.
We run into human-perceptible relativistic limits in latency. Light takes 56ms to travel half the earth's circumference, and our signals are often worse off. They don't travel in an idealized straight path, get converted to electrons and radio waves, and have to hop through more and more hoops like load balancers and DDOS protections.
In many cases latency is worse than it used to be.
as you point out so vividly, the speed of light is actually not a problem given you can ping across an ocean in sub 100ms (not a laser beam, actual packets through underwater pipes). 56ms is acceptable latency for realtime video
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.
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 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.
Are there many people involved in follow the sun support or SRE roles there? I know my company only has an engineering presence in Aus and Japan because of the large coverage gap between the US west coast and the EU. Seems like low wages + native English* could be a nice win for companies.
* For some definitions of native. I've had to work as a translator for a Kiwi and an American, both native English speakers.
> Seems like low wages + native English* could be a nice win for companies.
It's not always native English. It's always at least proficient enough, but a good chunk of the workers in the tech sector speak English as a second language. NZ has very diverse population.
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.
Depending on skillset $150k-$230k is common. You do have to balance this against the cost of living though, we definitely don’t have Eastern Europe’s cost of living advantage.
Assuming $ is NZD and you are quoting net, yearly income, then it is 1.5-2.5 times higher than Eastern Europe wages according to statistics in my environment. Unfortunately, cost of living has increased substantially here as well. For example, a decent (but not spacious) 2-bedroom apartment is in the range of EUR 300k-500k already.
That’s gross yearly income, after tax it’s $125k. Though for a lot of people there aren’t many other expenses after tax, just rent and food.
A decent 2 bedroom apartment in Auckland or Wellington will set you back $800k-$1.2M based on a quick look at the market. It can be a lot cheaper away from the cities.
The library does this in during runtime, though, if I’m not mistaken? The original commenter is probably referring to a build step that extracts the Lottie content and only leaves JS and SVG in the final output (which is not the case, as the Lottie web player library itself needs to be included as well, to render the animations and provide interactivity APIs during the rendering of the web page).
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.
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?