I have fond memories of using GitLab CI in 2018–2019 and I'm still pissed GitHub didn't just life and shift that kind of a model. Not sure about the particular issues you're running into but I remember GitLab supporting a lot of the YAML features missing in GitHub like anchors in order to build/compose stuff.
For similar reasons many years back when I broke the bank for a G2, I decided to disconnect it forever. Besides the always-on spyware, every update broke something, which is incredibly frustrating considering the amount I spent. For instance, I got a GX soundbar for free with the TV which worked fine for 1–2 months until some update borked it and made it glitch out randomly. To date, none of their updates seem to have fixed it. I now only connect it back to the web — if needed — once a year or so but even this needs plenty of careful research across the web to see if the update package breaks something else I take for granted.
Hooking up an Apple TV 4K to this thing was the best decision I ever made and the sheer performance of this thing puts every TV vendor to shame. I would recommend everyone to do the same if they're already in the Apple ecosystem.
I agree ive hooked up apple tv to override the crappy subsidized smart tv built ins that spy on you. That works until apple changes leadership and new leadership starts significantly mining data and caring less about privacy. It will happen at some point, not on Cooks term but someone else im sure of it.
While I've left my now fairly old TV on the internet, I use optical (TOSLINK) out to a cheap class D amplifier, which seems to have been a more reliable system than any of the HDMI audio based ones.
Maybe related: I bought an LG TV in 2014 or so, I was interested in what its calls home communicated, so I MItM'ed it to capture the http (no s!) traffic. I never did bother to analyze the requests and responses..
But I got a newer LG model 2 years ago, I was still redirecting requests to LG's servers to a local web server (using DNS), but I guess due to https, the certificate checks failed and the attempts to call home failed. This meant that I never got asked to agree to the T&As.
I am currently using one that is prevented from connecting to the internet via firewall rules from my router and all media comes from a separate jellyfin server. Had to allow enough of an internet access to install the app but once that was done, everything going outside lan is blocked.
Also most tvs have usb ports so maybe either raw media or some third part dongle can service as well?
Also also, most tvs of this caliber have hdmi you can plug your computer to.
Yes. I just got a new LG C3 OLED. I skipped the guided setup, then disabled any “smart” video manipulations. I connected it to an Apple TV, made sure the ATV’s remote worked, and Velcroed the LG remote to the back of the TV. The TV works great and hasn’t yet nagged me for internet access.
This just makes me extremely concerned for the iCloud transition I’ve been making. It shouldn’t be this easy to perform a user-disruptive action from the support/ops side. I would think they’d have visibility to some sort of “reputation” metric, given the age/purchase history etc even if anonymized.
I can understand this happening if it was a freshly created account topped up with a sus gift card but it’s unacceptable that the first action is to completely block an account with history.
Even more concerning is the nonchalant support response to “go create a new one” with emojis. C’mon Apple — this is just a terrible way to respond to this situation.
A lot of fraud bans are just automated in my company. Apple probably outsources Customer service to the lowest salary places they could dump it to, and call it a day.
> Then they rediscovered PHP, Rails, Java EE/Spring, ASP.NET, and reboted SPAs into fullstack frameworks.
I can understand the dislike for Next but this is such a poor comparison. If any of those frameworks at any point did half the things React + Next-like frameworks accomplished and the apps/experiences we got since then, we wouldn't be having this discussion.
> If any of those frameworks at any point did half the things React + Next-like frameworks accomplished and the apps/experiences we got since then, we wouldn't be having this discussion.
This is interesting because every Next/React project I see has a slower velocity than the median Rails/Django product 15 years ago. They’re just as busy, but pushing so much complexity around means any productivity savings is cancelled out by maintenance and how much harder state management and security are. Theoretically performance is the justification for this but the multi-second page load times are unconvincing.
From my perspective, it really supports the criticism about culture in our field: none of this is magic, we can measure things like page-weight, response times, or time to complete common tasks (either for developers or our users), but so much of it is driven by what’s in vogue now rather than data.
+1 to this. I seriously believe frontend was more productive in the 2010-2015 era than now, despite the flaws in legacy tech. Projects today have longer timelines, are more complex, slower, harder to deploy, and a maintenance nightmare.
I remember maintaining webpack-based projects, and those were not exactly a model of simplicity. Nor was managing a fleet of pet dev instances with Puppet.
Puppet isn’t a front end problem, but I do agree on Webpack - which is one reason it wasn’t super common. A lot of sites either didn’t try to bundle things or had simple Make-level workflows which were at least very simple, and at the time I noted that these often performed similarly: people did, and still do, want to believe there’s a magic go-faster switch for their front end which obviates the need to reconsider their architectural choices but anyone who actually measured it knew that bundlers just didn’t deliver savings on that scale.
I still remember the joy of using the flagship rails application - basecamp.
Minimal JS, at least compared to now, mostly backend rendering, everything felt really fast and magical to use.
Now they accomplished this by imposing a lot of constraints on what you could do, but honestly it was solid UX at the time so it was fine.
Like the things you could do were just sane things to do in the first place, thus it felt quite ok as a dev.
React apps, _especially_ ones hosted on Next.js rarely feel as snappy, and that is with the benefit of 15 years of engineering and a few order of magnitude perf improvement to most of the tech pieces of the stack.
It’s just wild to me that we had faster web apps, with better organizarion, better dev ex, faster to build and easier to maintain.
The only “wins” I can see for a nextjs project is flexibility, animation (though this is also debatable), and maybe deployment cost, but again I’m comparing to deploying rails 15 years ago, things have improved there as well I’m sure.
I know react can accomplish _a ton_ more on the front end but few projects actually need that power.
We are having this discussion because at some point, the people behind React decided it should be profitable and made it become the drug gateway for NextJS/Vercel
This is what I asked my small dev team after I recently joined and saw that we were using Next for the product — do we know how this works? Do we have even a partial mental model of what's happening? The answers were sadly, pretty obvious. It was hard enough to get people to understand how hooks worked when they were introduced, but the newer Next versions seem even more difficult to grok.
I do respect the things React + Next team is trying to accomplish and it does feel like magic when it works but I find myself caring more and more about predictability when working with a team and with every major version of Next + React, that aspect seems to be drifting further and further away.
I feel the same. In fact, I'll soon be preparing a lunch and learn on trying out Solid.js. I'm hoping to convince the team that we should at least try a different mental model and see if we like it.
With all due to respect to the folks working on Antigravity, this feels like a vibe-coded VSCode fork to me. Font sizes, icon sizes, panel sizes are all over the place (why?). To top it all off, the first request just failed with overload/quota exceeded errors (understandable, but still).
Looks like I'll wait to see if Google cares about putting the polish into a VSCode fork that at least comes close to what Cursor did.
The UI is certainly buggy, and things are getting fixed all the time. Guess it was more a "let people try the agent manager" instead of overfocusing on looks.
