thomaslord

I also think the Safari is just a very cool looking pen. I haven't really gotten into writing with fountain pens much as of yet, but I saw a Safari in a store and bought it based on looks alone.

If you're building one API endpoint per frontend view to avoid doing multiple API requests, your frontend and backend aren't decoupled anymore. I personally wouldn't say it's a bad thing, but if the best way to solve the issues of a decoupled frontend is to couple it to the backend again then I don't think that counts as an argument in favor of decoupled frontends.

I think there are pros and cons to this. I can definitely see how, in a company with larger teams, separating the frontend and backend can help with productivity. On the other hand, I'd wager that decoupled applications are less efficient with API calls something like 90% of the time.

When I build a fully-coupled application, loading any given page after the CSS/JS files are cached requires a single HTTP request which always includes exactly the data that's required for that page. When I've built decoupled applications, I frequently end up doing 4+ HTTP requests to load various pieces of data that don't make sense to include in the same API request. In some cases these API requests will depend on data from a previous API request, which leads to multiple sequential round-trips before the page is fully usable.

I started out at my current job working on a fully coupled system that's basically as "legacy" as you can get, and eventually started modernizing it - as part of that process, we decoupled the frontend from the backend. At first it felt more productive simply because it wasn't the old system and the new frameworks actually had documentation, but once I compared it to building a coupled system with modern frameworks I realized the coupled system made me much more productive. I'm currently the only developer at my company, though, so I feel like I'm probably the perfect target audience since I don't have to worry about team coordination at all.

Fortunately with modern serverless architecture, it's possible to make this performant! Just split up each comment into words and dispatch each word to a queue where AWS Lambda workers can check the words against the user's password hash. It might cost $20 to process each comment, but at least it'll autoscale to handle any comment volume you throw at it!

I feel like this term should be repurposed to refer to lifted trucks that never leave pavement

Any idea if these projectors could be made to work with other sources that don't require DRM? As much as this sucks for movie theaters, it could also be the deal of the century for a home theater build if you know the right people...

I also think a person who has had to strip out or replace dependencies is more likely to be careful when choosing them in the future. This is definitely the case for me, at least.

The problem is that humans are bad at sitting there paying attention while they're not actively engaged, which is what's required to use FSD safely. Also, FSD has essentially no benefits if you use it safely. If you listen to someone talk about what they want FSD for, they'll probably tell you they want to be paying attention to something other than driving or that they want to sit in a more comfortable position where their feet aren't on the pedals and/or their hands aren't on the steering wheel.

The current Tesla FSD beta has no purpose other than as a tech demo, but people absolutely treat it as if it's ready to be your chauffeur while you take a nap in the back seat.

I do think cofounders, particularly cofounders with specific skillsets who could be earning a solid salary at a more established company, have additional barriers. Being a cofounder means giving up "I'll definitely make X" for "Maybe some day we can sell for 1000X", so you need to find someone who's willing to take on the risk and fully believes in your plan.

Honestly in my brief dabbling with ChatGPT, it hasn't really felt like it's good at the stuff that I'd want taken off my plate. At work I tend to build stuff that you'd describe as "CRUD plus business logic", so there are a decent number of mundane tasks. ChatGPT can probably fill in some validation logic if I tell it the names of the fields, but that doesn't speed things up much. I work primarily in Laravel, so there's not a huge amount of boilerplate required for most of the stuff I do.

The one thing I was really hoping ChatGPT could do is help me convert a frontend from one component library to another. The major issue I ran into was that the token limit was too small for even a modestly sized page.

I don't have a handy article to link, but US vehicle loan terms have been steadily increasing for a while now. Many people end up rolling negative equity into their next loan, which can push them into choosing something more expensive for their next vehicle because the lender has a limit on what percentage of the new loan can be rolled-over negative equity.

My suspicion is that this trend is driven by long loan terms, high interest rates, and loans being larger than the cost of the vehicle.

To be clear I agree that your setup should be supported, but I have to ask... How do you have those set up? I've seen people with a random smattering of monitors, but typically it seems like that happens with smaller/older monitors. I'm not sure I've ever heard of someone having so many different aspect ratios/orientations all in one setup.

If you go far enough away from the nearest city that housing prices drop, median income drops as well. I'm not saying I'm surprised that housing in NYC is expensive, but I live in the suburbs of Philadelphia (specifically in one of the cheaper areas that's still close enough to commute into the city) and housing is expensive here too.

T-Mobile has been rebranding themselves as the "rebel" of the cell network industry for a while... Maybe someone can convince them to parody this by releasing a "5,736G" network?

I don't know if much innovation is really required, honestly. You probably won't find what you're looking for with Mac/Windows, but if you run a tiling window manager like i3 on Linux you'll pretty much just see a clock, some system stats, and whatever applications you have open on the screen. You can pretty easily configure the bottom bar to remove the superfluous system stats, or even the clock if you want.

Is that the kind of experience you'd look for in a distraction-free OS? If not I'd be interested to hear your ideas - I use i3 for work but manage to distract myself anyway because I always have a web browser open.

I imagine that economists probably correct for inflation when putting this data together. I can't speak for these graphs 100%, but I think the real issue we're talking about here is not money or people but resources. Resources can be roughly mapped to people, with the confounding factor that each person consumes a different level of resources. As we approach the resource limits of our planet (and potentially nearby planets) that confounding factor becomes less relevant, because we eventually won't have enough resources available for anyone to consume more than they strictly require to stay alive.

The problem is the ecosystem. You can get response times for the main page down pretty low (especially with caching plugins) and the time to serve static assets is the same for Wordpress or a static site. Most likely if your site feels slow, the culprit is your theme and one or more plugins on your site. You can usually track down problem plugin(s) using PageSpeed Insights since their frontend assets are served from the plugin folders.

I don't think you're quite getting what really causes these safety issues. Limiting cars' acceleration or speed still leaves 6000lb SUVs with double the momentum of 3000lb sedans. Most car crashes don't involve anyone going 100mph, but heavy SUVs with bad visibility are frequently involved in accidents.

Because they're technically "offroad vehicles" (even though most of them never go offroad), SUVs are allowed to ignore many pedestrian crash standards. The NHTSA also crash tests vehicles against other vehicles in the same class, so the true consequences of SUVs don't show up in their tests.

There's also the issue of children being run over in driveways and parking lots by SUVs with massive blind spots.

Ultimately I don't think they can. How would they handle a link like `https://example.com/password_reset?prid=ZXhhbXBsZWNsaWNraWQ`?

I'm sure somebody will figure out a way to use multiple seemingly-legitimate parameters to get the same result. Why use ?click_id=aqNERjsdfyqe when you can use ?category=10612550&subcategory=5929127&page=4257344 and transfer the same data without arousing suspicion?

Yeah, even if ChatGPT could perfectly understand the prompts you'd still run into major issues with token limits. I tried to get it to rebuild a single page for me (to move from one UI framework to another) and I couldn't fit the existing code in the token limit. I might be able to get it to do a chunk of the initial work for a greenfield project if I perfected the prompts, but it's structurally incapable of maintaining existing code.

Car guys recommend Toyota because someone who's asking what car they should buy probably just cares about affordable maintenance and not having their car in the shop all the time. If you just want to get from point A to point B, Toyota is probably your best bet.

If you ask what car would be the most fun to drive, or have the best interior comfort, you'd probably get a different answer.

I still think these numbers are too low, at least for my metro area. $60k post-tax in the Philly metro area isn't enough to rent a decent place alone and also save for retirement. Maybe when they say "take-home" they're assuming that number is after paycheck deductions for healthcare and 401k, but they should definitely specify that.

A large part of the issue is the modern Javascript ecosystem too. The browser isn't the most efficient way to build apps, sure, but using a virtual DOM adds a whole extra layer of performance issues.

With Reddit specifically, I think they at least have one legitimate reason in addition to the normal nefarious ones. Their new web interface is incredibly slow, especially as you continue browsing over time. On phones, that's likely to cause more serious performance issues than it does on desktop devices.

Unfortunately many of the people who fled Russia are vocal supporters of Putin. Those people support the war, but don't want to be drafted into service themselves.

Obviously this isn't everyone who has fled, but I think it's important to note that having left Russia doesn't necessarily mean someone doesn't support Putin.

I just took a look at Gunicorn and, while I'm probably a bit biased as a PHP developer who also maintains the infrastructure, I think setting up PHP is almost exactly the same as setting up Gunicorn.

The Nginx config will look a little different, but it requires roughly the same number of lines in the config file. In both cases a first-time user will probably be doing a Google search for a tutorial and following that tutorial, and in both cases it's pretty much as simple as copy/pasting in the installation commands and then copy/pasting the Nginx config and modifying it to suit your use case.

PHP has the advantage of allowing you to use shared hosting if you really want to, which is great if you're just getting started. Definitely not what I'd want to use for anything resource-intensive, but at least there's a way to build a basic site without setting up the server yourself.

I'll second the advice to learn Laravel!

PHP has gotten a lot better over time. For someone who hasn't used it since version 5 or earlier, writing modern PHP with a modern framework like Laravel will probably feel like whole new language. Speed has improved substantially, especially throughout the 7.x releases, and the type system has improved a lot as well.

Laravel itself is a great framework with amazing documentation, and it should be very easy to get started. The one thing I'd warn anyone who's written "old PHP" about is falling into old habits. It's easy to write the same old spaghetti code and jam everything into the controller, but your code will be much more readable if you do some practice projects and intentionally expose yourself to the modern way of doing things. If you've been using other languages in the meantime, this may be an easier transition for you.

This isn't meant to be a dig at you, but iCloud seems like an interesting choice for someone who cares about visible folder structures, given that Apple led the pack on hiding files and folders from their users. I'd be curious to know whether you evaluated a bunch of alternatives or settled on iCloud because you already had an account and it was just an easy choice.

Disclaimer: I would definitely say I have a personal bias against Apple.

In my opinion, Windows and Mac OS are similarly bad for web development. Mac OS comes a little closer to the Linux environment I prefer using, but you'd probably eventually run into something that was a pain to get working. I never had this issue myself because I haven't tried using Mac OS for professional development, but I did have an intern who had trouble getting PostgreSQL installed (I tried to help with no luck).

With how common Docker is getting in development workflows, I think it's probably the best option for developing on either Mac or Windows. I think the big difference is that Docker will run natively on Windows whereas on a new Mac I believe you'd probably end up running through Rosetta. I strongly recommend Docker over the linux subsystem for windows - having tried to use the subsystem for professional web dev work, you'll probably run into some weird glitches eventually.

My company was forced to move from our previous G Suite plan to Google Workspace. In order to keep the same monthly price, we went with Business Starter.

Now each user can only share a Google Doc with 5 non-Google users per month. This limitation seems entirely artificial and designed entirely to push people onto more expensive plans.