121–130 of 142 posts
Earlier quoted context omitted.
quaternions - 1843, Hamilton projective geometry - 1420's but big in the 19th Century. These are things I used heavily programming earth mapping systems in the mid 1980s to mid 1990s. Principal reference text was from the 1920s.
... The guy I responded to is saying Pythagoras is good enough. Do you know what year Pythagoras died?
Earlier quoted context omitted.
>We abandoned HTML CSS and JS websites that used to work just fine Hmm. Have you actually done much web development in the last 10 years? Building websites with raw HTML, CSS and JS 10 years ago was very much not "just fine". There's a reason frameworks were invented.
What do you consider "not fine" about websites written in "just" html, CSS, and js?
Earlier quoted context omitted.
What do you consider "not fine" about websites written in "just" html, CSS, and js?
1) Rats nest of non-declarative JavaScript. 2) Rats nest of JavaScript callbacks. 3) Overlapping stylesheets with !important everywhere. 4) Elements used for style not their semantic purpose ( , ) 5) Subtle and not-so-subtle browser compatibility issues.
Earlier quoted context omitted.
Wait till you hear about Typescript, you know adding types to ECMAScript, like Macromedia did some 20 years ago. :) Being in the industry for 20+ years and starting as a teenager making games in Flash it makes really hard for me to treat webdev seriously with all their revolutionary innovations. At work I often encounter a resistance to a tech or solution I propose, because "there hasen't been any substational contri…
Unless you are ready to maintain the product for the long term, proposing to use new tech is just resume development.
Two months later that staff member left the BigCo for another organization, and when we found the actual job posting for his position the X, Y and Z were explicitly stated as nice to have for a candidate.
¯\_(ツ)_/¯
Earlier quoted context omitted.
Wait till you hear about Typescript, you know adding types to ECMAScript, like Macromedia did some 20 years ago. :) Being in the industry for 20+ years and starting as a teenager making games in Flash it makes really hard for me to treat webdev seriously with all their revolutionary innovations. At work I often encounter a resistance to a tech or solution I propose, because "there hasen't been any substational contri…
I'm glad to have mostly avoided frontend dev, but we've also had some bonkers backend trends like SOAP. It was like closing your eyes and wishing for a full-stack impl to appear if you write enough XML.
I work with ton of json, including hundreds of kubernetes definitions per project, and I really miss the ability to parse the data so swiftly and effective with native syntax.
Earlier quoted context omitted.
I'm glad to have mostly avoided frontend dev, but we've also had some bonkers backend trends like SOAP. It was like closing your eyes and wishing for a full-stack impl to appear if you write enough XML.
Actually, one of the things I miss the most from AS is... E4X. I work with ton of json, including hundreds of kubernetes definitions per project, and I really miss the ability to parse the data so swiftly and effective with native syntax.
Most XML experience I had was ejabberd and XMPP. Was thoroughly pissed off by the end of it. We ended up sending JSON over IQ messages instead because we were super done with XML, only to find that iOS's XML parser takes O(N^2) time to parse each element. Had to split the elements to make it work. 0/10 would not recommend.
Earlier quoted context omitted.
Actually, one of the things I miss the most from AS is... E4X. I work with ton of json, including hundreds of kubernetes definitions per project, and I really miss the ability to parse the data so swiftly and effective with native syntax.
I've never used E4X, but it at least looks like it'd make XML more tolerable. Most XML experience I had was ejabberd and XMPP. Was thoroughly pissed off by the end of it. We ended up sending JSON over IQ messages instead because we were super done with XML, only to find that iOS's XML parser takes O(N^2) time to parse each element. Had to split the elements to make it work. 0/10 would not recommend.
Earlier quoted context omitted.
Wait till you hear about Typescript, you know adding types to ECMAScript, like Macromedia did some 20 years ago. :) Being in the industry for 20+ years and starting as a teenager making games in Flash it makes really hard for me to treat webdev seriously with all their revolutionary innovations. At work I often encounter a resistance to a tech or solution I propose, because "there hasen't been any substational contri…
> Being in the industry for 20+ years and starting as a teenager making games in Flash it makes really hard for me to treat webdev seriously with all their revolutionary innovations. I think the framing here is unfair. It's not that the people innovating in JS or HTML think what they're doing is "revolutionary" or has never been done before. Generally they are applying ideas that have been developed elsewhere, but ar…
(1) Some time ago I'm at a coding interview and I'm tasked with an algorithm to calculate the biggest rectangle you can make of a set of segments. Or something similar. I'm presented with a computer, with VSCode, with an open file with some code already. I left my chair, approached the whiteboard available in the room and started thinking about how to address the problem. The interviewer was not pleased with my approach and eventually after I exchange my thought process he invited me back to the computer, asked to write some code, and when he saw I was doing for loops with vars he interrupted me, pointed at the beginning of the file which was "import lodash" and showed me the expected solution. A lot of functional mambo jumbo which was obviously very sexy at that time.
I looked at his code and asked him what's the computional complexity of his solution. He looked at the code, thought for a minute and said the session is over.
(2) About that time I was doing a web app that was a huge web form. The user could exit and resume a session at any given time so the input was stored in database and was supposed to be retrieved when the session resumed.
At one point I noticed that the initial loading time was noticeably slower, and after inspection it turned out that the init time raised from zero to about 800ms. It was the same time when our senior JS programmer with 9 years of experience shipped the code that was responsible for retrival of the data from the backend.
It was functional masterpiece. No loops, lots of map and reduce and he was very proud of it.
When I pointed out it had O(N^6) complexity and could be fixed with a simple for loop matching ids he got offended and stated that "we don't program that way anymore, functional is the future".