vonseel

I bought my iPad 5th gen years ago pretty much for reading PDFs. Sadly, it's barely even usable for that, even after a fresh device reset it's laggy and so slow. I'm not sure if it was always that way; I don't think so. I've stopped upgrading iOS but I think I'm already at 15, if there's a way to go wayyy back that's probably what I want to do, but it's sad that even an iPad can be bogged down so much as to barely run PDF readers. And I always wished mine supported pencil / annotations, but I think I'm one generation behind.

I imagine most employees who get by in cloud docs (Google/Microsoft/etc.) and don't really open apps other than browsers can learn to be comfortable with an iPad, but many people don't want to. I have friends who refuse to even learn to use a trackpad on Macbook because they are so set in their ways.

I’ve been viewing the cached result constantly

Doesn't everyone? I can't stand not using monospaced fonts when coding

I've seen it said that newsfeeds/ads/etc. feed you what they think you will engage with, so you may want to wonder why you're seeing that type of content. I've never seen anything of the sort on any large tech platform, and I'm probably in an appropriate demographic to be recommended that stuff.

For "Advanced" Web Programming, I don't really feel like you're hitting the mark by sticking with PHP. Sure, it works, and will probably get the job done for most web projects any of your students will ever work on, but if you want to get people excited while making them employable, it's important to teach new tools and frameworks. Unless the "Advanced" part is more about the techniques and patterns and less about the language, I think you're doing them a disservice by not branching out. And, of course, you can teach patterns and techniques in any modern language.

I'd expect to see some discussion of async job processing and front-end web frameworks in any advanced web programming course, high-school or college level. Honestly, just teaching the usual react stack with a typical node backend would probably be ideal since JS is approachable, react is still "cool", and you still only need to use one language.

Exactly how I feel reading this thread, I had no idea PHP has changed so much.

I was curious what kind of range that might have, so I put what you said into chatgpt and asked what the range of a typical car or home stereo would be, and it gave me this (not sure if it's correct). FWIW, much less than 20 miles, haha.

-- The maximum power output of a personal FM transmitter allowed by the FCC is 250 microvolts per meter at a distance of 3 meters. The range of the transmitter depends on various factors such as terrain, obstructions, and interference.

Assuming ideal conditions, such as no obstructions or interference, the range of the transmitter can be calculated using the inverse square law. This law states that the strength of a signal decreases with the square of the distance from the source.

At a distance of 3 meters, the signal strength would be 250 microvolts per meter. At a distance of 6 meters, the signal strength would be 62.5 microvolts per meter (250/4). At a distance of 9 meters, the signal strength would be 27.8 microvolts per meter (250/9).

Typical car and household stereos have a sensitivity of about 2 microvolts per meter. Using this sensitivity value, we can calculate the range of the transmitter for these devices.

For a car stereo, the transmitter would have a range of about 26 meters (square root of 250/2). For a household stereo, the transmitter would have a range of about 63 meters (square root of 250/0.5).

However, in reality, the actual range of the transmitter may be shorter due to various factors such as interference and obstructions.

Epic/Cerner/SAP may be CRUD apps with clunky and outdated interfaces, but I wouldn't classify them as basic. Those applications are massive and have a ton of legacy code to connect different things. I'd suspect much of the rest of their staying power does lie in the company's scale and relationships, as well as their domain knowledge. It would cost massive amounts to build a viable competitor to any of them, and you'd need people who understood the problem space well enough to know what code to write. Doesn't matter if it's just a basic CRUD app built on top of a standard RDBMS, if you don't know what features are needed.

> ow my feed is like 10 percent science, 10 mildly racist / inflammatory content, 10 percent miscellaneous,

So basically it's the new Facebook

As if CS is the only major in jeopardy of this? I predict the accountants and admin staff etc. will be replaced long before the people who build the systems that replace them.

I loveeee fd! About the only time I reach for find is if I need to do something with printf.

I’ve noticed a bunch of CLI tools recently released written in rust that are along this same line of being snappy and well-written. Fclones, ripgrep, paru, fd, exa, to name a few. This probably has more to do with the type of developers the rust platform attracts, rather than the language itself (many awesome tools have been written in go recently as well). But yea, devs who have an interest in Linux and command line tools tend to be great IMO :)

Europe energy prices :/ Here in Texas it cost maybe $5/month to run a 45 watt little server (pc)…

On 1 - I've worked at startups using Django ORM and banking companies using MSSQL stored procs. I don't understand why anyone would ever go the stored proc/raw SQL way unless they absolutely needed the performance. And if you do need the performance, you can always dip down to that level from whatever ORM you are using.

Most of the queries I've done using Django can be optimized at the application code level to be fast and efficient without even touching SQL. There were a few instances at the two Django shops I've worked where we optimized one or two queries by writing raw SQL, but the number of times I've seen that in a codebase can be counted on one hand.

The SQL/stored proc method, on the other hand, doesn't come with any way to do migrations or version your database by default (AFAIK). So now you have to write migration code and come up with some kind of versioning system by hand.

Wish I had more experience with SQLAlchemy/Alembic. I've tried using it on little things here and there but since I've always known Django, that's what I usually go with.

Correct. And most people back then were just using `pip install -r requirements.txt`, including different files for dev/test/prod as needed.

I worked at one company that used buildout back then, which seemed relatively rare, but buildout was more flexible and allowed you to do things like installing system packages or running your own scripts. We used it to pull down config files that weren't checked into the repo but still wanted to be shared, helping setup the local developer environment, and a few other things.