The one I saw most recently was working with an SRE coworker. Data in what looks like a table, in this case a subdomain/IP address, that overflows the cell gets cut off with no ability to actually view it. I almost had him just edit the CSS in Chrome, but he figured out a different workaround.
Yes. We’re beginning the process of moving away because of how they’ve become a single point failure that’s unreliable. AWS is more reliable and it’s a bad spot to be in when your CDN / router is down but your actual application is fine
These acquisition announcements always leave me uneasy. There’s a lot of hand waving, “nothing will change and our roadmap will stay the same!” but we can all do basic math and understand that’s not how business works.
As an aside, I have to use Cloudlare at work and it’s a pretty awful experience for the medium sized org I’m at. “Hostile UX” is a common complaint. Maybe they should invest money in competing with Vercel on UX/DX instead of acquiring open source projects.
I lived in Japan and your level of written fluency paired with the patience to distill aspects of Japanese culture strikes me as AI. Even amongst long time foreigners, there’s this unspoken “we’re not explaining this to you, figure it out yourself.”
Your level of fluency would be incredibly rare, and I’ve never seen any Japanese person use romaji in casual online conversation.
“Gunma Banker Mode” would 1) be an insane commute to Tokyo where most banking occurs 2) is strange for someone who says they’re not a programmer, but a banker who is “switching their OS.”
Lastly, your comments just stink of AI because you point the obvious out in not—so-correct ways. “Code” is not the context, but I can see how HN could be reduced to that.
If both are true — this is an AI article and people are commenting with AI, then I fear peak dystopia is upon us and HN is losing its magic to information pollution. Sad times
I don’t really see what’s newsworthy. Acela already runs in the NE corridor and many trains have outlets. Other than the 27% increase in trains, it’s hard to tell what’s different
I’m not creating a medium account to read the entire article, but I read plenty of bad code while living in Japan — as a full-time employee, a contractor, and open source projects. I would take this article with a grain of salt.
I’m mixed about Next.js. On one hand, it’s a company building a framework with investors, of course there are incentives for them to corner the market. Like the author mentions, Redis labs has a similar model. The license is MIT, so Netfify or anyone can fork and offer a better alternative, if they’re capable and willing to take on the risk of it flopping. Also, if I’m an investor in Vercel — why would I encourage them to put my investment at risk by aiding competition?
On the other hand, there does seem to be a sleight of hand with Vercel. They want it both ways — to be a company that champions and fosters open source while also keeping the necessary friction in place to make their hosting platform the best choice.
For better or worse, I think we’ll only see more of this model in the future.
I think linux + osx combined is probably developer majority. I'm assuming most Windows development is .NET or Unity based. Over the past nine years, I've worked primarily with Node, Ruby, and a smidgen of Java and no employer has issued Windows machine. It's in sharp contrast with the start of my career where I was in VB6 and C# where I only worked with Windows environments. Could be confirmation bias, though.
I passionately disagree with this. Abstractions inherently introduce some level of opaqueness and it's only useful in the context of making things more maintainable. Duplicated code is easier to reason about because its intent is closer to the problem it originally solved.
I chose TypeScript for a large project for the first time in early ~2018 and had no idea how much history I had missed. I presumed that the adoption was the other way around and that TypeScript was chosen because it fit the project's needs, but just as grandparent and parent suggest, AtScript was very much a thing.
I'm currently on one. Was very burnt out from high stress environments and not practicing enough self care for the past five years. I experienced daily bouts of mild to intense anxiety despite being what most people interpret as a calm person. Reasoning, I was laid off and decided to not take a job.
I took unemployment.
Positive benefits: I mellowed out, started having more patience, and could see how a big source of burnout was how attached my ego was to my work.
I started working on a link shortener a couple of months ago. Despite it being a hobby project that a lot of folks undertake, building something resilient that is somewhat well-designed is a lot of work. Biggest benefit: I started looking at programming as more of something that I'm capable of instead of my self worth / value on display in pull requests.
> Did you return to your old job?
Nope.
> Would you have done anything differently?
More routine. It's liberating to be able to do what you want, as you want, but I would posit that a majority of humans thrive on routines.
> Is there anything bad out of the sabbatical that you didn't expect?
Friends and family being concerned for my well-being despite my spirits being much higher
In my experience, using a service like Cloudflare or Fastly creates a gap between what you're working with locally and in pre-production environments. It quickly becomes a single point of failure, but you can offset some of this with having a staging environment that mirrors production alongside e2e tests.
Admittedly, it's pretty hard to roll your own DDoS. If I was on bare metal or a service that doesn't provide its own DDoS protection, I would absolutely use something like Cloudflare despite all of the downsides.
Like others have mentioned, this seems to be from ~2016. The lack of HTTPS on the provided link ages this some for me, but the use of coffeescript really dates this[1]. I even thought coffeescript had been deprecated, but it does seem that the project is being kept alive[2] which is really cool.
Perhaps, what is most interesting is that it took nearly 4-5 years for the front-end community to collectively come to the conclusion that SPAs are not _always_the answer. I don't think the zeal for SPAs came from a bad place either. I can remember how poorly ASP.NET and other frameworks of the 2008-2012 era packaged an overcomplicated way to pass data to view layers. There's lots of curmudgeon-ining from non-frontend folks but, in my opinion, the lack of performance and ergonomics with existing frameworks, combined with the newness of Node.js is what brought about the explosion of tooling and frameworks.
There is a place for SPAs, though. VS Code, Spotify, and other apps that need a desktop / browser experience to feel like a mobile app are great candidates. Twitter, for example, shouldn't be a SPA or SPA-like application. I find that it frequently over-caches content and will randomly refresh my feed at times while I'm browsing. It feels as if a simple web page that needs to deliver more JSON responses as I scroll is trying to do too much.
JS land really needs to take some notes on how Rust and Go handle major versions, i.e. avoid them if possible. Breaking changes may be progress for tooling but for end users it's upgrade hell.
Ruby ~Rails~ found the middleground where major/minor versions[1] typically land in December. Rails[2] typically follows which gives users ample time to upgrade along with a migration guide