My unpopular opinion is that computing is stuck in a local maximum based on technology from the 1970s. In particular, typing into an 80x25 terminal window with unformatted fixed-width characters should be obsolete; we don't need compatibility with punch cards any more. There was a thread a week ago about displaying graphs in your terminal using ASCII graphics. This shouldn't be necessary! Also, code shouldn't be a se…
So instead of editing and compiling text files what should we be doing instead?
Ask HN: What's your unpopular tech, programming opinion
21–30 of 61 posts
Re: Ask HN: What's your unpopular tech, programming opinion
#22We need operating systems that enforce file selection, instead of deferring to the applications. This is known as capability based security, and most people think of "allow access to X" on their phone, which is NOT what I mean.
When you want to open a file, an application shows a system supplied dialog box, then goes ahead and opens whatever the heck it wants with the full trust of the OS, no matter how wrong that is.
All I'm asking for is the OS to handle the file dialog and pass a capability (like a file handle) to the app instead of trusting it blindly.
The downside is that unless there are clever shims, this requires rewriting everything.
---
The reason we have VMs then Docker then Containers is that our Operating Systems don't enforce capability based security, and we've been improvising a replacement for it in this manner.
Re: Ask HN: What's your unpopular tech, programming opinion
#23Re: Ask HN: What's your unpopular tech, programming opinion
#24These tools allowed domain experts to get a GUI tool built in a matter of hours, and for the most part, those solutions just worked.
Microsoft Access 2000 managed tables and relationships automatically. You could have master/detail relationships multiple levels deep and it all just worked. It did queries well enough, hooked to SQL via ODBC, and did pretty good reports.
It was a pretty cool environment when you tied it all together.
- Then Microsoft got obsessed with .NET and Borland got greedy, and ruined it
On the Web side of things, there were WYSIWYG Web editors that worked in much the same fashion, with a whole stack to support it. You could lay out a Form, and have a CRUD app running on the web in short order.
- Then Ruby on Rails came along, and ruined it
The main thing we've gotten in the past decade is faster hardware, especially thanks to SSDs, and GIT. GIT is amazing, but don't be fooled into thinking it actually stores deltas, it just acts like it does. GIT is a snapshot tool, way better than stacks of floppy disks/USB sticks labeled Archive001 -- Date
Re: Ask HN: What's your unpopular tech, programming opinion
#25Earlier quoted context omitted.
So instead of editing and compiling text files what should we be doing instead?
I don't have the solution; I just see the problem :-) Programs could be in some sort of database rather than a set of files, so the code you're interested in gets displayed without you caring about how it is broken down into a sequence of lines in a file. Sort of like how a database shows you the data you want, rather than needing to put entries in the right order. You shouldn't need to think about how your methods a…
page 4 https://www.google.com/books/edition/Mastering_ENVY_Develope...
Re: Ask HN: What's your unpopular tech, programming opinion
#26My unpopular opinion is that computing is stuck in a local maximum based on technology from the 1970s. In particular, typing into an 80x25 terminal window with unformatted fixed-width characters should be obsolete; we don't need compatibility with punch cards any more. There was a thread a week ago about displaying graphs in your terminal using ASCII graphics. This shouldn't be necessary! Also, code shouldn't be a se…
Programs written using the Win32 GUI and forms still work decades later. Its a shame there isn't an equivalent in the Linux world.
---
We should have rich source text by now. You should be able to freely time comments, include notes, links, images, etc. in the source code of a program, and still have it compile correctly.
---
We should be able to directly modify the Abstract Syntax Tree of programs, renaming as it is stored in the tree would cause it to correctly change the name of every use with zero errors. Refactoring this way would be much faster and more reliable.
Re: Ask HN: What's your unpopular tech, programming opinion
#27Re: Ask HN: What's your unpopular tech, programming opinion
#28Every time I hear someone wanting to rewrite something without a VERY solid reason is a flag for me. It is hard improving a system that’s already there, but can be super rewarding if you change your mindset.
Everyone is eager to go with a blank canvas and greenfield a project but ultimately we’ll end up with the same shit situation in 5-6 years after the original authors have bounced and the newer devs are side-eyeing the code.