HN user

OutsmartDan

540 karma
Posts1
Comments58
View on HN

Love Sublime and have used it since its inception long ago, however as the times changes with different built-in convenience tooling (such as AI), Zed has overtaken Sublime IMO. It's fast, has VIM mode, extensions, and takes away some of the hassle that you have to go through with ST.

I still use ST for basic editing, but for day-to-day, Zed is the go to, simply because it just helps me get my work done slightly faster.

PS I still pay for a ST License every 3 years <3

Pressing command+k, attempting to find a solution to an issue- but the solution is for app routes not pages route.

Having them separate was better for documentation satisfaction.

The new docs are extremely annoying; if you're still running a legacy app, sometimes you get put into a doc for a feature you think exists, but then you realize it's not for the right version you're running.

Also the new app routers are very confusing. There are concepts of a layout, template, page, etc. While it's nice to have server rendering at this level, it's difficult to understand what is bubbling which direction, and when to use a layout vs a template. Sometimes after building something one way (eg using layout), you realize you actually need to build it using the other in order for specific features to work.

Old Next was great and simple- new Next has become increasingly frustrating and not so easy to adopt.

The crucial difference is keeping the address bar- this is where I think Arc is falling short. Maybe it's me, but I have an extremely difficult time reprogramming my expectations of where the address bar should be.

Before next, server-side React was a nightmare. They've simplified it a bit by providing Next.

It would be wise to decouple Vercel, the company, and Next, but Next as a framework itself is great to work with at scale.

I’m trying to love GitHub Actions, however, when builds and tests randomly fail on custom runners when they’re configured the exact same and there’s no option to debug, it becomes painstakingly frustrating. We’ve tried most of the big CIs, Travis/CircleCI/codeship- and while GH Actions integrates nicely with GitHub itself, it’s a far less superior product compared to its peers.

There are better ways to gather feedback, even if your application is in beta. Most loyal customers will let you know what’s wrong and what features they’re most excited about- that honest feedback is far superior than telemetry data. You can even add a survey form after the application exits to try and maximize the feedback loop.

Totally understand you’re a new venture backed business, however, you most likely are targeting the wrong group of users by automatically sending data over the internet for “no reason”.

That's a ton of data being collected. I would rather much have this submitted during a crash, rather than opt-in/opt-out. I'd not want to use a terminal that has data collection that crosses the internet every time I use it.

[dead] 5 years ago

Lessons learned: DNS Redundancy shouldn't be an afterthought.

-DNSimple customer

At this point, Darklang just seems like an over glorified side project. I cannot see any real business creating an entire backend system out of darklang- the learning curve, vendor lock-in, and volatility of the project is not worth the risk.

Developers hate these tools for a reason: they're the ones maintaining it after it's been deployed. The whole concept of "no-code website builder" ultimately goes back to "where is the code and how do we modify or integrate it with our current systems".

Maybe if it was marketed as a "fast prototyping" tool, I'd be more on board with the product.

I would argue that reset style sheets or normalizers should be part of your "minimal web dev" process, even if you roll your own version. There are so many browser nuances that these things fix so that you don't have to hack it later down the line.

Imagine you are in a cave, for no apparent reason, and your computer is no where to be found. The only computer there is a n old school terminal that is somehow running IE11. Your colleague commits something with tabs instead of spaces and you get the notification on your phone. Now you can easily login to VSCode online to re-indent everything with spaces, commit and push it back up, all through your web browser.

As an avid cyclist in NYC, this is a huge step forward into cyclist protection. I can't tell you how many times i've almost been hit, or doored, by a car. Sometimes, it's a lot safer to run a red light to get in front of a car versus waiting for the light to turn- but of course that's not legal.

Honestly, as huge and condensed NYC is, I am surprised this hasn't happened years ago. It's much, much more efficient to get from Point A to Point B on a bike vs taking the Subway, bus, or car. Would love to see something like the 14th street car ban to allow buses and cyclists only more widely adopted across the 5 boroughs.

Yes, I would rather the page be blank and load correctly rather than having content replaced while I'm actively looking at it. This pattern should be an anti-pattern, but I would assume they probably have a KPI to decrease site load time by a percentage versus a better product experience.