When you bet your whole career on Flash and time moves on

Description

The meme is split into two horizontal panels separated by thick black banners. Top banner text: "Flash developers in 2008". Under it, a bright-colored Doge (the famous shiba inu) sits on a white background looking proud; to his right the caption reads, with the original typos preserved, "Macromedia Flash is amazning! I will become become Flash web developer and devote my whole career to this". The lower banner reads "Flash developers now" and below it a grayscale, worried Doge stands in a dim, leafless forest, conveying despair. The joke contrasts the 2008 excitement around Macromedia/Adobe Flash with its 2020 end-of-life, highlighting how betting a front-end career on a proprietary browser plugin has aged into a legacy-systems cautionary tale for modern web engineers

Common Tags

LegacySoftware LegacyCode WebDevelopmentHistory Frontend DeveloperRegret TechNostalgia DeveloperMemes

Comments

Anonymous ★ Top Pick Somewhere in a dusty SVN repo sits 800k lines of ActionScript, still hoping WebAssembly will eventually add “desperation” as a compile target

Anonymous ★ Top Pick

Somewhere in a dusty SVN repo sits 800k lines of ActionScript, still hoping WebAssembly will eventually add “desperation” as a compile target
Anonymous

The real tragedy isn't that Flash died - it's that somewhere out there, a Fortune 500 company still has a critical business process running on a Flash app that nobody wants to touch, and the last developer who understood the ActionScript 2.0 codebase retired to become a goat farmer in 2019
Anonymous

This meme perfectly encapsulates the existential dread of realizing you've become a domain expert in a technology that's now as relevant as COBOL on mainframes - except COBOL developers still have job security. At least Flash devs learned the hard lesson about vendor lock-in before betting their careers on Google's next messaging app
Anonymous

Specializing in Flash was the original monolith: one runtime, one vendor, and one very large single point of failure on your resume
Anonymous

Flash taught me why ‘avoid single points of failure’ applies to careers too - when your runtime gets EOL’d, your entire stack becomes a migration plan and your title auto-refactors to Senior React Engineer
Anonymous

Flash devs post-Jobs keynote: 'Timeline mastery? Nah, just another React hook jockey now.'
@pyproman 5y

Ruffle: I'm gonna resume this man's career
1. @maxgraey 5y
  
  From https://github.com/ruffle-rs/ruffle/wiki/Roadmap#milestones AVM1: ~70% compleate AVM2: 0% compleate After 4 years of development. Unfortunately too slow
@s2504s 5y

Yamldevelopers - you are here
@alissonlauffer 5y

hoping the same thing happens with javascript
1. @asoteric 5y
  
  you dont have to download sketchy self deleting installer bloatware to run javascript ill probably be around forever
2. @nyttevaerdien 5y
  
  +++
3. dev_meme 5y
  
  Why tf you hate js this much?
  
  @RiedleroD 5y
  
  yo I can understand him, definitely. It'd be so much nice to be able to script with python or something else that's remotely sensible in a browser.
  
  dev_meme 5y
  
  How came that python is more sensible than JS?
  
  @alissonlauffer 5y
  
  Language: js Source: console.log(999999999999999999999 === 1000000000000000000000) Result: true
  
  dev_meme 5y
  
  You will have SAME issue in ALL languages who follows same standart for numbers with floating point
  
  @RiedleroD 5y
  
  ye, but converting ints to floats is madness
  
  @RiedleroD 5y
  
  e.g. python uses bigints (or something similar, anyway) per default. Meaning it doesn't fuck up simple integer calculations, unlike js.
  
  dev_meme 5y
  
  No, Python do not use bigint by default :)
  
  @RiedleroD 5y
  
  dude, I mainly code in python. I kinda know what I'm talking about over here. python doesn't have any rounding errors when handling huge numbers, and you can have infintely large numbers (as long as you have enough memory space).
  
  dev_meme 5y
  
  Yes, but looks like you missed what is BigInts
  
  @RiedleroD 5y
  
  explain then
  
  dev_meme 5y
  
  Just google and in English, proper term for how Python store number is BigNum. In this approach you do not just store number, but you store each digit separately
  
  @RiedleroD 5y
  
  and how does that differ from BigInt?
  
  @RiedleroD 5y
  
  from the MDN web docs: BigInt is a built-in object that provides a way to represent whole numbers larger than 253 - 1, which is the largest number JavaScript can reliably represent with the Number primitive and represented by the Number.MAX_SAFE_INTEGER constant. BigInt can be used for arbitrarily large integers. no, that does kinda sound 100% like what I just described.
  
  dev_meme 5y
  
  To make it simple: BigInt have limit, other than just memory
  
  @p4vook 5y
  
  because it sucks
  
  @p4vook 5y
  
  because web becomes worse and worse because of javascript
  
  @doodguy1991 5y
  
  HTML/CSS website: FAST AF AND LOADS ON 56kbps Javascript website: takes 30 seconds to load on 100mbps

Use J and K for navigation

When you bet your whole career on Flash and time moves on

Description

Categories

Common Tags

Comments

More like this

Adding Cybersecurity to a 30-Year-Old Legacy App Is Pure Cosmetic Theater

Java 8 Refuses to Become Outdated Despite Every Developer's Wishes

The Pain of Modernizing the Wrong Legacy System