prinny_

The advertised point is it needs zero config to work outside of the box. For example nerd fonts are included by default whereas you need to install them if you are using let’s say iterm2.

Kagi.

> Why should I go through so many layers to get my CSS

You underestimate the passion with which the average front end developer hates CSS.

I think it’s a very good look when the people you complain about are racists.

This may be a low effort comment but I just wanted to say that there was a missed opportunity to call this project Spotifast.

I eagerly await the day we can fully style the date & time component so that we can put all those JS libraries to (a well deserved) rest.

Can you please expand on why what Orion does is hacky and may cause issues with other add ons?

I agree for famous authors. But I also believe you are overestimating the average person when it comes to their ability to articulate their thoughts.

I believe there are some programming jobs in which the code is absolutely the easier part. Not all of us work in signal processing, integrated systems or have to push upstream to Linux kernel because the company we work for really needs a memory allocation optimization for its data centers.

Navigating customer requirements and building something that satisfies both market's needs and company strategy can be an incredibly difficult and frustrating problem to solve. Especially if you need to also oversee the execution of the strategy. So not only you have to predict what they want or know the domain deeply enough to understand what they say they want is not what they really want, you also have to come up with a plan for executing your solution in a corporate environment.

There is a reason that books like "the staff engineer's path" cover topics such as local maximums, communication, establishing support for executing a plan or creating alignment on big efforts. In large corporate environments with multiple international customers, code is most of the time not the hardest problem.

I like working from the office for the same reasons. Makes my home feel home and keeps my workplace out. However, I also used to commute for an hour and a half just to go to the office and another hour and a half to come back. This I don’t miss at all.

They expect a sort of breakpoint at which each subsequent model version will only be marginally better than the previous ones, thus allowing them to retain their value for some time. Their business doesn’t work if each year the new model demolishes the previous one in terms of performance.

I guess an interesting use case for this would be to pinpoint exactly which change was made by who in cases where multiple people / agents work on the same code at the same time. The Zed team is working on two features that are probably going to be built on top of DeltaDB: async collaboration and instant sharing. Instant sharing used to be talked about more in the past and it's still the feature I am most eager to see.

From an engineering perspective slow is smooth is fast, but from a sales perspective slow is smooth is slow. If you quote superior quality with 6 months later delivery your competitor will get to sign a contract that could very well last 5-10 years and comes up just so rarely. Missing out on that contract doesn't always mean you get to focus on other projects, it could mean you have to fire whole teams of people that you don't have anywhere to assign anymore.

From my perspective a failure point is when companies do delegate time to make things correct, but demand results from the get go. Billing and tracking becomes weird for them if you work on infrastructure, design systems, component libraries, system design etc and you have nothing to show for after 6 months or a year. "But the future development will be super fast" doesn't fly past upper management unfortunately.

The value of FE unit testing is inversely proportional to the amount of mocking in said tests. I once worked on a complex admin dashboard with lots of business edge cases. The unit tests for the forms and the settings didn’t have any mocks and therefore we could catch legitimate bugs. On the other hand I have worked on code bases with so much mocking that I couldn’t make the tests to fail by intentionally bricking the component.

AI slopping my config is what allowed me to learn vim without going through the pain of setting it up. I can ask AI to teach me about some motions or set up some configs for m in lua without ever know lua. This is the biggest impact of AI in my professional life.

Does it matter if the response is tone deaf or simply misguided? I am a bit nihilistic here, but in one week absolutely nobody will be talking about this. Are the affected individuals going to abandon instagram? Are people going to reduce their usage out of concern for the safety of their accounts? Nothing will happen, hence there is no need for actual humans writing a good, well intended response.

WASM is not for games specifically, it's for anything that needs native performance but also needs to run on the web.

Interesting. Can you please elaborate more? Is it due to the combination of popular foundation (js) and the addition of strong typing? The runtime environment differences? The ease of integration with other languages / tools?

> A word to web devs. I hate your crap.

I would like to say I agree with the proposition of your post and your arguments, but as a web dev please don't mix the state of the web with what the median web dev considers a good UI/UX. We don't make the Jira tickets and if you have worked in a corporate environment you know very well that arguments like "but the UX/accessibility" hold very very little value in the context of most decisions.

I believe there is a middle ground here. Quick calls can definitely mess with your flow in your day to day work, but ruining multiple hours of “in the state” is either an overstatement or the author may be best suited for a different role that demands less communication.

On the other hand modern application of agile methodology is borderline ruinous for team productivity and most of the time exists for a specific stakeholder to feel less anxious rather than for a team member to raise a blocker or a dependency.

I work in a fairly big company and there is the notion of extracting people from their agile teams to have them work uninterrupted on large tech initiatives. Which is in my opinion a subtle way to signal that if you know what you want to build, agile methodology at least in the perverted way most companies apply it doesn’t work.

For people like him who probably already have enough money it’s probably just chasing the opportunity to work at the bedding edge of the field he loves. And maybe get to be the father of AGI.

Only issue is what happens when the company that owns the search and has a dominant share of the browser market flags your site with the good old "warning: potential risk ahead" when people try to reach it directly? And buries the "I know the risk let me through" deep in the browser settings. Advocate for different browsers? Google is pushing web attestation in one form or the other. I wish the future would look bleak, because right now it's looking blue, red, yellow and green and it's worse.

You're allowed to exist on the web. The alternative is you are pushed out, your site is not indexed and google / chrome labels it as a security risk when people are trying to reach it directly. The mandate is clear: give up the data or give up the spot.

Is it expected to be hard? Meta currently employees a lot of people who are willing to be there for any number of reasons. If 2 years down the line Meta announces a hiring push offering the same or better compensation packages with the ones offering now I am sure people will flock to be there.

I think we should put behind us any discourse about companies risking their hiring pool by being hostile to the society or their own employees. People will definitely try to be hired at $company if it means six figure pay, doesn't matter the sector. We have plenty of examples for this.

I doubt AI can educate the masses simply because the masses would have to prompt it to educate them. Almost no one in my social circle knows, let alone understands Google’s recent work on pushing web attestation, or any other tech company’s power plays enforced on us. They are people blindly hitting accept all in every banner that pops up in their online journeys or use chat apps that blatantly spy on them.

They don’t know what they could have or why the new captcha is funny, thus they can never come up with a prompt that leads to them being educated on the matter. They would have to know that they don’t know and since there is no public discourse for such matters in their Facebook timelines, their thinly right wing digital news outlets and their Viber and what’s app chats they will never know that they don’t know.

I have been following zed for quite some time and I use it daily alongside nvim (haven’t yet tried zed vim mode, planning to). I really like the performance and control zed provides, as well as the reduced UI clutter compared to alternatives. The collaborator functionality is not talked enough by the community but I believe it’s an ambitious idea worth pursuing. Wishing the team all the best.

I think it’s a nice feature. I use it to have designs on one part of the screen and implementation on the other. That way I can jump between “designs | implementation” and “PR | swagger” without managing and resizing tabs. Previously I had to jump between tabs and taking into account the newer screens provide a considerable amount of UI real estate there was screen area to utilize.

Vercel promises to engineer the pain away when it comes to deployment. The thing however is that Vercel introduced that pain in the first place by writing sub-par documentation and splitting many of NextJS functions into small parts with different cost.

Everyone trash talking the JS ecosystem without contributing the slightest to the conversation would benefit a lot if they read https://www.artmann.co/articles/30-years-of-br-tags in order to understand the evolution of the language and its tooling.

Nobody argues what we currently have is great and that we shouldn't look to improve it. Reducing it to "JS developers bad" is an embarrassing statement and just shows ignorance, not only of the topic at hand, but of an engineering mindset in general.

I believe if you read this article https://www.artmann.co/articles/30-years-of-br-tags your "wtf is wrong with js developers" question will be answered.