ardit33

Seems very similar when Microsoft invested in Apple back in the day when Apple was about to die. Their concern was that they would be the only one OS company standing and be defacto a monopoly and regulated such. So, it was a away to keep your 'weak' competition alive just enough not to make you the sole provider.

Steve Jobs was able to turn around Apple in such a fashion that they become even bigger by letting go of the PC market and going mobile.

Nah... I do like them. I like having an ultrawide monitor, and curved is a must .

This is some weird logic. "I dated someone that didn't like to work on child care and therefore I don't think universal childcare is a good idea".

Yeah, I dated someone that was a teacher and didn't like her job. Doesn't mean that we shouldn't provide education to kids.

Youtube is being overloaded by such playlists. They become obvious after listening to them for a bit. There is something jarring in them which makes them kinda annoying.

You must be young. XML and XML Schemas existed before JSON or Protobuf, and people ditched them for a good reason and JSON took over.

Protobuf is just another version of the old RPC/Java Beans, etc... of a binary format. Yes, it is more efficient data wise than JSON, but it is a PITA to work on and debug with.

JSON exists, and when compressed it is pretty efficient. (not as efficient as protobuff though).

For client facing protocol Protobufs is a nightmare to use. For Machine to Machine services, it is ok-ish, yet personally I still don't like it.

When I was at Spotify we ditched it for client side apis (server to mobile/web), and never looked back. No one liked working with it.

lol.... development speed and quality are both the bottleneck my dude. But if you have enough speed, you can fix quality issues as you are able to test and fix things faster.

You have even CEO of car companies that get fired because they mess this up. Or even the Sonos company lost a lot of value, and got their CEO fired because they messed up and can't fix it in time.

Speed is not everything. Developing the right features (what users want) and Quality are the most important things, but development speed allows you to test features and fix things fast and course correct.

Amazon culture is only viable because the H1B system. I worked there (yes I was on H1B), and they made sure to delay any green card conversion at every step possible in order to keep you there longer.

If they were unable to abuse it, they'd be more employee friendly.

yeah, this is the exception since it is a dev tool. Not sure Apple will approve a regular app doing it.

lol... you really don't like it, do you. I used it for a couple of my projects, and I kinda agree with you. I didn't like it at all how it took over projects (you have to use a workspace).

For my small personal projects, eventually I ended up into reverting to just downloading the dependencies myself into a lib folder. A bit more work upfront, but simpler builds and you know what's going into your project.

I think it had its use and time, and it is good for the maintainers to mark it deprecated and time to move on.

This is a problem for folks with sensitive data, and also for coorporate users who don't want their data being used for it due to all kinds of liability issues.

I am sure they will have a coorporate carve out, otherwise it makes them unusuable for some large corps.

LLMs help a lot in doing 'well defined' tasks, and things that you already know you want, and they just accelerate the development of it. You still have to re-write some of it, but they do the boring stuff fast.

They are not great if your tasks are not well defined. Sometimes, they suprise you with great solutions, sometimes they produce mess that just wastes your time and deviates from your mission.

To, me LLMs have been great accelerants when you know what you want, and can define it well. Otherwise, they can waste your time by creating a lot of code slop, that you will have to re-write anyways.

One huge positive sideffect, is that sometimes, when you create a component, (i.e. UI, feature, etc), often you need a setup to test, view controllers, data, which is very boring and annoying / time wasting to deal. LLM can do that for you within seconds (even creating mock data), and since this is mostly test code, it doesn't matter if the code quality is not great, it just matters to get something in the screen to test the real functionality. AI/LLMs have been a huge time savers for this part.

Well, at least it is a video. Meta had its layoffs with emails when they did all those rounds in 22-23 and 24. You got an email if you were safe, and another if you were terminated plus some links to some portal etc. Plus, there was some video/zoom call for some I think.

Anyways... modern corp culture, don't expect too much from larger companies. Once a company grows beyond a certain limit, it becomes impersonal as it has to.

Macromedia Fireworks was the modern predecessor of these tools that ushered web graphics back in the dot com days. It was bought by Adobe, and shuttered around 2009.

I loved that tool

Next is a Superman videogame being blocked because it goes against the 'policies/interests' of a country that manages to lobby a lot here.

It is still incomplete and a mess. I don't think they thought through the actual main cases Swift is used for (ios apps), and built a hypothetical generic way which is failing on most clients. Hence lots of workarounds, and ways to get around it (The actor system). The isolated/nonisolated types are a bit contrived and causing real productivity loss, when the old way was really just 'everything ui in main thread, everything that takes time, use a dispatch queue, and call main when done'.

Swift is strating to look more like old java beans. (if you are old enough to remember this, most swift developers are too young). Doing some of the same mistakes.

Anways https://forums.swift.org/t/has-swifts-concurrency-model-gone... Common problems all devs face: https://www.massicotte.org/problematic-patterns

Anyways, they are trying to reinvent 'safe concurrency' while almost throwing the baby with the bathwater, and making swift even more complex and harder to get into.

There is ways to go. For simple apps, the new concurrency is easy to adopt. But for anything that is less than trivial, it becomes a lot of work, to the point that it might not make it worth it.

1.So far, it is great if you know what you want, and tell it exactly how you want it, and AI can help you on that (basically intern level work).

2. When you are in a new area, but you don't want to dive deep and just want something quick and it is not core of the app/service.

But, if you are experienced, you can see how AI can mess things up pretty quickly, hence for me it has been best used to 'fill in clear and well defined functionality' at peacemeal. Basically it is best for small bites, then large chunks.

Buying in NYC is just wild. A condo can have a 400$/mo tax, while the next door one is 1300/mo, and the other one down the street can be only 35$/mo for the first 20 years.

There is also a mortgage tax of 2.05% for a loan, which is batshit crazy as it favors rich 'cash only' people, instead of middle class / poor folks. Also, everything over 1m has a 'mansion' tax, where a 1m gets you one bedroom, without even a washer and dryer, and also there is a 'new building tax' which is another 1% or 2%.

For a 'not new' smallish 2bdr, 800sfq, in Greenpoint, the cost of purchase was 1.3m-1.35m and just the closing costs (taxes and all) was 55K! Just to buy a place (not talking about downpayment and all).

With a current rates, you'd end up paying 9k-10k for a basic (10 years old) 2 bedroom, which is insane at any levels.

Anways, end of my rant. The city needs to both build more, and lower taxes for residents, and raise them for anyone that is not a NY resident. Period. But the builders have resisted this, and Cuomo the coorporate stooge gorvenor we had vetoed/ended a initiative to have good taxation that favors residents.

Building more and giving tax breaks to anyone (even foreginers/non state residents), is just a hand out to developers, and 1/3rd to those apartment will be used a 'storage' for outside money. Locals loose on this.

So true... out of the 5 games I have bought on steam, I have played 2 (one fully), and installed and just played briefly 1, and two other never even installed.

Agreed... in most large (non trivial systems) REST ends up looking/devolving closer to RPC more and more and you end up just using get and post for most things and end up with a REST-ISH-RPC system in practice.

REST purists will not be happy, but that's reality.

Man, there are street that are closed to traffic, and you just are either lying or being dumb.

They just don't look like streets anymore, as they are turned into plazzas or parks.

EG: E25st at Lex, Baruch College is truned into a plazza/walkaway. No cars. 8th/st Saint Marks, by A Ave, is off cars, (It is part of the Tompkins park). Irvin Avenue is part of a park (gets interrupted by Grammercy Park)

etc...

There are plenty of places like that, but over time they turn into plazzas or parks, and you think they were not streets at some point.

Ps https://maps.app.goo.gl/Df6U3DkPpUxirG5B9

https://maps.app.goo.gl/ZivSNhiEnn2Q4pjr6

You can see throw time that it used to be a street at some point.

Anyways, there are plenty of examples like that. Just stop exaggerating.

Not true. E25st by Baruch college has turned into a plaza. There are some more, that I can think off. (8th/St Marks by A Ave, is a park) etc.

This used to be a regular street at some point https://maps.app.goo.gl/ZivSNhiEnn2Q4pjr6

There are plenty of other examples, just now they look more like plazas, and not streets.

Most of BUS lanes in NYC are not fully occupied. 2/3rd of the time they are just sit empty.

But, I agree on the part that they will slow down a bit existing public transportation, but, if Uber served routes that are currently difficult to reach, it has public service as well.

Why would someone pay $10 for the Uber service, meanwhile the local one is just $3? There is a good chance that the local bus doesn't cover certain areas properly, or stops too frequently, making it a slow trip for regular commuters.

Ps. In Europe there is both public and private trains, both running the same tracks. I don't see a problem with this.

Good idea for certain routes: But

"like between Williamsburg and Midtown in NYC" -- That's route is baffling and probably not needed. There is already a subway, (L then Transfer to 1-6 lines, or R/W). During peak hours, the subway is faster.

This is juvenile thinking... none of them will go away. They can be independent services themselves, and be pretty profitable at it.

The upshoot is if they are independent, they will be forced to compete fairly with other services. Which, does increase competition and choice.

You are making my point... if you have to use ViewRepresentable in half of the app, then SwiftUI failed. It was supposed to completely replace UIKit, but now it is just another framework to work with...

(makes easy things super easy, but harder/complex things harder).

It has some ways to go......

They have stalled, and the concurency is making things harder to implement right.

Basically, Vapor has to be re-written as it is, in order to work will with swift 6+. Which kinda kills already any little moment it had.

Was looking to use it with a new project, as it is a nice framework, but going with GoLang on the server side due to all this in flux changes.

Maven was the one the started the downfall into dependency hell. (Ant as well, but it was harder to blindly include things into it)

Kids today don't know how to do that anymore...

I don't use the new concurrency features, as they are one of the main culprits of this mess. (so stick with 5.x)

SwiftUI is a wreck, that is still not good for advanced UI and you still have to use UIKit for some parts, and

Taking Objective-C, with DispatchQueue, and some modernization of it, and some new data structures, which it need, was all it was needed to make a good new langue.

It could have been Apple's rival to GoLang, but instead it ended up being hydra/monster with too many pardagimns, and none of them are good.

It is not just the language but the frameworks. SwiftUI is a wreck, and still not mature even after 6-7+ years in 'production'. You still have to drop to UIKit to do advanced UI, and for what it is, SwiftUI is just not practical enough for cases that are not trivial. The trouble is that all new kids/engineer are learning it first, which means software wont get better. Apple need to improve it first, and I don't see advanced folks ditching UIKit anytime soon for advanced UI.