reflectiv

my current job still uses it deep in some abstraction created ages ago...

AI in general at the time was led by a VP and a particular group (that was AI tech specialized) under him. The initial idea came about from them. We were trying to find new ways of using AI to research new sources of crude at the time.

Another AI project I worked on there was a chemical tank use estimation and refuel application which used tank sensors, previous use history and some other metrics to pre-purchase and deliver product to keep tank reserves above a certain threshold.

For context, all of this was circa 2018-2021.

I was a developer at Shell a couple years back and led a project where we were using nascent GPT-1/2 to process and search over mountains of documents. It was a fun project where I wrote a complex/fancy UI for a stratigraphic filter and indexing system...

Seems this is just a natural progression...neat.

...and its been hugged to death in minutes.

What kind of stupid statement is this...no it certainly does not.

But humor me with an explanation, please...

The 'light-based' network thing kinda threw me for a second...wifi IS technically light, its just a frequency (RF) at which we can't see it and that can (somewhat) penetrate walls.

His timeline sounds exactly right to me, I basically did the same thing.

Mid-late 90s I used Beej's network programming guide to write an IRC client.

> Which sites do that for any meaningful reason?

Literally none...this is just the argument of contrarians or people who've only ever worked on personal projects who take offense to real applications used by actual audiences.

> I actually can't imagine any other use for vh that isn't related to screenjacking

Creating fixed panels on the left or right side of the viewport that are full height and sticky.

I think we're making a supervillain recipe here guys...chill

Yes, I do this too...its a different thing when you are talking about your own insular project or something at a smaller scale.

The thing I was talking about was larger scale projects like the ones mentioned by the author (of the sort I work on at my day job) where you have teams of stakeholders and outside influence combined with a desire to release rapidly in an iterative form.

Software these days is just done differently in those contexts...we can't slow down enough to do what was detailed above...I just wish the world was sorted in a way or slowed down enough to do REAL engineering.

I really wish software was written this way these days.

These days I am always being rushed through sprints barely knowing what is going on.

What you described sounds like a wonderful way to actually engineer a great API.

Yea...

DO has some really great documentation for their services so I am hopeful they will only enhance/make-better css-tricks.

Each environment should have its own keys for the services it is talking to so ideally this would restrict the scope of damage.

Ease of use is a separate topic from money no matter how much you want to try and mix the two.

Yes one is often at the cost of the other...but they are different topics.

Just wanted to say your grandpa sounds pretty damn cool

This is basically what I tell people when they ask me why I put my start menu and task bar on the left side of the screen.

mobile is much more akin to desktop development because the API's/etc are specific to each device type (android/iphone).

The web is a different beast from that too.

20 years is a bit much IMO...5-10 tho, that sounds at least reasonable.

ok but like....thats for desktop application development...

...this is the web, a completely different and totally unrelated beast.

I write web apps for a living and literally ran into this last week...and was promptly annoyed when I realized chrome was ignoring the attribute to disable it.

ok but that is github...parent poster stated its common to do that...it is not.

I especially love typescript when it comes to refactors or API changes...on my team we strictly type as much as possible and it has made refactors and API changes so much easier and fail-proof.

For example if an API change occurs on backend, the first step is to make the change to the request/response typings in the frontend...from there the source code will light up with all the errors you have to fix. I can just click through each one in VS Code and fix them, then re-run tests to validate...love it.

I am sorry...but what would the RIAA troll Github for exactly?

If it is a truly empty file then no, because that wouldn't validate as a valid html file.

The bare minimum I believe is <HTML></HTML> ...which on its own wouldn't be a HTML quine.

and a lot of them begin with 'perl is a mess...so...'

> This is such a stupid, frustrating argument to hear.

Reality is often frustrating, I agree.

Google started rendering pages before indexing a while back because of this...so generally it's ok from an indexing perspective (assuming you still have working URLs that can also be loaded in the same way for all your linked-to content).

They have to be forced to because they often refuse to.

It's really that simple...cry about it all you want. It's a necessary evil...because humans.

It's not about specialized knowledge...it's about regular maintenance.

Hate me or not...but people can't be trusted (broadly) to maintain things...thats just the way life works.