canyonero

> They were free to not buy items if they didn’t like the price

Customers are buying many goods at Costco one might deem as essential (food, toilet paper, etc) in bulk to save on cost. An illegal tax was being collected everywhere and likely at an even higher cost.

I think it’s reasonable for the author to feel like Frontend is a treadmill. It can at times without a doubt be tiring. It certainly was moving much, much faster in the 2010s (although, I think it started to cool down in the 2020s)

I don’t think this specific problem targeted at Frontend or Frontend frameworks is necessarily useful other than to vent. It seems this can be attributed as an effect of swelling technology communities. Frontend has been a community with explosions of ideas, high levels of participation and enthusiasm coupled with opportunities for notoriety and wealth.

One could argue that AI is currently experiencing a similar phenomenon as Frontend did in the 2010s. If it follows a similar trajectory, we’ll be seeing articles about AI treadmills.

Yeah, I don't buy this conspiracy theory. The reason why they charge it could be as simple as they calculated the bandwidth usage following a ddos attack. It amounted to 104k worth of bandwidth usage. There system is not sophisticated enough to recognize it was a mistake due to attack on their site. Thus a manual intervention was needed, and now it's resolved.

This is very weird take. I'm struggling to understand why this is incident as a reflection of "super negative practices" or is somehow a "scam". The CEO came here and publicly apologized for the mistake and mis-communication, and the issue is resolved for the user with no charges. What am I missing?

That's good to know. However, there was a ton more information that existed in the right hand panel that was pretty important for translating design to code that is now removed.

For as long as I've used Figma, I've been able to view the underlying CSS. This is no longer there. I can get it, but I have to copy/paste it somewhere else to see it. Very annoying. This existed before "dev mode" was a thing. I think it's fair game if you want to make this experience better in "dev mode" to differentiate, but to take away a feature like that is and then try to upsell it a money-grab IMO.

Ouch. My team got bit by this today. TBH, I haven't been following what's necessarily included in "Dev Mode" and what's not. But, it appears with this move that they have redacted one of the most essential features of design/dev collaboration. (The ability to inspect, color, spacing, dimensions). This has always been available, until now. It's a lot more expensive, too. Dev Mode is just a huge price increase with not much value add IMO.

This is really cold.

- Layoff during a time when employees should be relaxing and resting

- Executing the layoff covertly

- Replacing humans with AI bots

- Pulling the rug from under customers (leaked AI replacement with no official announcement)

How lovely. I can't see how this plays out well for Duolingo. I was actually considering getting a paid account in the new year, but now, not so much.

Speaking about the US only (w/o actual data to back it up, just a feeling over the last year) is that lower-wage jobs have been on the rise out of the sheer necessity for businesses to attract warm bodies. Folks in the middle (low-middle -> high-middle( have had their wages depressed and lowered while the wealthiest individuals have had no impact or have seen their wages increased at or beyond inflation. The combination of very wealthy folks doing better and the lower income earners having higher wages has created dissonance around the reporting in the overall health of the economy IME.

I enjoyed the writing and analysis of the team at 538 over the years. I don't plan to visit on the new ABC platform, sigh. Can anyone recommend some good alternatives?

Although, I was hoping for forgiveness to proceed. The decision is not really the upsetting part (for me). IMO the interpretations of the legal framework and decisions for SCOTUS often quite conveniently align to modern political party lines.

As I've mentioned in another comment, SCOTUS is compromised by political interests despite the facade of impartiality. The legal framework we have is no different than the bible or quran or any other text that has produces religions, political parties or ideologies. There are many interpretations one could make about such texts, but somehow judgement often is split by modern party affiliation. It was kind of cool to think for a while that SCOTUS was just doing their job and above political polarization. I no longer hold faith in that belief.

Disappointed by the outcome, but not surprised. IMO SCOTUS is no longer trustworthy when it comes to impartiality. Polarization has infected every branch of government including SCOTUS. This judgement simply falls along US political party lines. Perhaps, it has never been the case. However, I think we have seen an increase of conservative policy and interpretations of law become the standard due to a Republican super majority.

Oh cool. This is definitely something I'd consider if it's still around by the time she reaches an appropriate age. Thanks for sharing!

Giving children and teens unfettered access to social media and the internet seems to be more of a problem to me than any particular piece of hardware. The cell phone I had access to as a teen was a flip phone from Virgin Mobile that ran on "minutes". There was no web browser, no apps. I used it for texting and calling.

It's up to parents to control access to the content (unfortunately, the tools and hardware that exist for this sucks, which is unfortunate). So if you're dropping an unlocked iphone into your kids lap and walking away, well then maybe you're putting them at risk and neglecting them (which might be further causing mental health issues.)

My daughter is young now, but I will eventually run into this as she gets older. I've thought about this issue and I plan to lock down the content (either via software or targeted hardware) until she's an adult.

Good to get some other perspectives from OoT fans. I played it multiple times as a kid. No other video game came close in terms of the connection. It was the perfect game IMO.

My interest in video games declined greatly as the trend in the video game industry shifted toward heavy violence and more realistic graphics. Fast forward to last year, I decided to pick up the Switch as I found one for a really good deal. I wanted to try the new (to me) Zelda. I felt pretty unimpressed, decent not great. As it turned out, I had mistaken the much hyped BoTW release with the Zelda release that I bought. I was playing Skyward Sword.

Once I realized my error, I picked up BoTW and took it for spin. I now think the hype is totally justified. I got all the feelings I felt with OoT. It's been wonderful so far. I'm only about halfway through and stocked for Tears of the Kingdom.

Personally, I wish we could stop judging individuals without understanding the context. There may be a million different reasons for someone that needs frequent job changes in a four year periods. Asking good questions to candidates will be far more informative and useful to the business than having a set of rules for dismissal or judgement.

Furthermore, the company is rarely/never accountable for swiftly laying people off individuals that may otherwise be excellent workers.

Frankly, if a company is discarding CVs based on perceived loyalty, then I perhaps those same companies to provide candidates with a contract reciprocates that loyalty via generous raises and job security.

I'm with you. I've never found the "used by $BIG_NAME_COMPANY" to be influential for me at face value. But anecdotally, I think that level of marketing has been effective in getting devs to bring them up in that context. I've heard in meetings throughout my career, devs saying: "It's good enough for $BIG_NAME_COMPANY, it'd be good enough for us". That alone has influenced decision makers to at least consider it.

Non-paywalled version - https://archive.is/kQ6Hl

> The best ideas and collaboration happens at the office.

Care to back that up with some data or evidence? Otherwise, you're just blowing smoke.

> After using Vue 2 as our front-end framework for almost two years

So a rewrite in less than two years? And Vue 3 was announced over two years ago: https://blog.vuejs.org/posts/vue-3-one-piece.html

The original decision, to me, feels like the wrong one and with no long-term thinking considered. They are now making another poor choice based on framework-hype.

I've been sensing this coming for some time given what Rome has been working on. Will be interesting to see how the rewrite pans out!

Any discussion these days around eslint reminds me of a new situation that still has me very confused where I've encountered a team of engineers that refuse to allow any formatting on their code. Are there any folks that run large JS/TS codebases with no automated linting/formatting by choice and maybe feel similarly or worked with other teams that do? I've come to expect eslint (and prettier) to be pretty much a given for a large JS/TS codebase.

One feature for code search that I've wanted for some time that could unlock some really interesting results would be to allow search to reach into the git file history.

I've found myself sometimes thinking that something existed in a particular codebase and I go to look for only to discover that I'm unable find it. Then, I realize that the code I was looking for has been removed. I can only find it by browsing back into the history figuring out the events that led to the deletion or change. Being able to search the history would be killer IMO.

I’ve not seen any evidence of the most influential voices in my network moving now that Musk is running it, but it’s still early I guess.

I really value some of the opinions and discourse I find on Twitter. However, I despise Musk, his brand and vision. I’m torn, but I’m planning to discontinue my Twitter usage and evaluate if there is a successor in 3-6 months.

A lot of folks associate Vite with Vue or React. But the ease of use and overall dev experience in a vanilla TS/JS and web components is fantastic.

IMO when paired with Vitest, the setup feels powerful, modern and lean. Would recommend.

My experience as an engineer with ~10 years of experience (4 of which working remotely):

I've seen no data that'd indicate a meaningful shift yet. I've also seen no shifts from recruiters reaching out to me about in-person roles. All recruiters reaching out highlight that the positions they're looking to fill are fully remote. (I receive anywhere from two to ten outreach messages per day)

That said, my experience doesn't mean that there isn't or won't be a shift, but I haven't found or observed any evidence yet. I believe there is still an abundance of work for engineers wanting to work remotely right now. The remote opportunities are far, far better than any time previous to 2020.

This is wonderful and IMO the answer to the “broken” software dev interview. Leetcode is a hazing ritual that needs to end.

My engineering org focuses on tasks that are as real-world as possible. Areas we evaluate on:

- Have the candidate update some code based on a feature request close to real world requirements

- Have the candidate do some code review

- Have candidate describe how they productionize an app

> If you're considering using one of these frameworks, I would recommend you carefully consider if the complexity is worth it, especially for less-experienced members of your team.

Far too many folks seem to believe that complexity is a binary choice or that it can be avoided wholesale by choosing frameworks (or lack-thereof) to solve their problems.

Truth is, when you're building software on the web, you're gonna have gonna have to make a series of decisions on where the complexity that you'll inevitably encounter should live.

We're all simply making tradeoffs on where that complexity lives: the browser runtime, the build system, the type system, the server, the platform, their framework, your framework.

> Would you recommend RedwoodJS for green field projects?

IMO if you want to run PostgreSQL, React and GraphQL with the least amount of friction and decision making, RedwoodJS is great choice.

> How would you say an opinionated framework like this works in the medium to late maturity?

If you run a frontend-heavy and/or TS/JS shop and don't mind the tradeoffs of something like Ruby on Rails, then I see no limitations to building whatever you want with it.

> Is it easy or even possible to switch out components with more "enterprisy" solutions?

Not sure what that would look like, so I can't comment.

I've used both and I can say some key differentiators are:

- The routing is quite different. RedwoodJS handles routing in a single file rather than doing file-based routing.

- Next.js is full-stack available while RedwoodJS is full-stack by design. A Next.js developer needs to make many decisions about how they will design their API (the DB, GraphQL vs REST, choosing an ORM, etc). RedwoodJS is more opinionated and provides Prisma, *SQL, and GraphQL out-of-the-box.

- RedwoodJS has code scaffolding out-of-the-box. You can easily scaffold out models across frontend and backend based on your Prisma/DB schema.

- Next.js is intentionally designed to have first-class support on Vercel whereas RedwoodJS is by design, more agnostic toward to the deploy target.

From their main website (https://redwoodjs.com)

“Redwood is the full-stack web framework designed to help you grow from side project to startup.”

It's seeming pretty fashionable these days to bash SPAs. I disagree that SPAs were mistake (or that it's often a mistake to reach for a SPA, even today) SPAs are now and have been a great tool to leverage when you want to build an application without needing to think about servers. Yes, there are tradeoffs. Yes, you should think about the thing you're building for. Yes, you should think about the skills of the developers working on it. That doesn't change the fact that SPAs can be great choice and not something to be perceived as a mistake.