It's Game Over For FarmVille, as Flash Also Buys the Farm (bloomberg.com) 110
The last day of the year was also the last day for FarmVille, one of the original addictive Facebook games. From a report: FarmVille, which allowed players to cultivate colorful cartoonish farms by tending crops and caring for livestock, had 30 million daily players at its peak. But game developer Zynga announced in September it would shut down the game on Dec. 31, a victim of Adobe's decision to stop distributing and updating its Flash Player for web browsers, which in turn led Facebook to announce an end to support for Flash games on its platform.
Aww (Score:3)
Awww ..how sad .. it couldn't have happened to a better game :(
Re: (Score:2)
Farmeville! It's just as much fun as being a real farmer. only without the benefits! [youtube.com]
Re: (Score:2)
Incredible political power including access to generous welfare should you elect a conman who obliterates your business in a dumbass trade war?
Re: (Score:2)
Sheep, goats, and their related products together only amount to 0.2% of US agriculture sales.
Keep looking, there might be even more benefits to farming.
Re: Aww (Score:1)
Re:Aww (Score:4, Insightful)
Re: (Score:2)
Re: (Score:2)
There is no shortage of cutesy farming games, like Stardew Valley.
Flash EOL (Score:2)
Re: (Score:2)
:-\
They got what of a return on investment?
Re: (Score:2)
"sheâ(TM)ll". That's how much of a return they got. I'm not sure how that translates into Earth currencies, but it's about a bleevix.
Re: (Score:2)
They created Farmville 2 as a mobile app and Farmville 3 as an HTML 5 app. It was a good excuse to upgrade the graphics and cycle out a lot of old content. But it was definitely a business decision.
Re: (Score:2)
Re: (Score:2)
And the security issues.
HTML 5 also is critical to advertisers as it allow them to run animated content on users browsers without consent. However HTML 5 does not have the same security issues and has other uses.
Re: (Score:2)
Flash was critical to advertisers because it would run animated content without the users ability to stop it. Until flashblock. Which made it obsolete.
And the security issues.
HTML 5 also is critical to advertisers as it allow them to run animated content on users browsers without consent. However HTML 5 does not have the same security issues and has other uses.
HTML 5 still allows annoying videos that people don't want. It's up to the user to figure out how to block them.
Re: (Score:2)
when Steve Jobs arbitrarily killed it on ios
No, that isn't quite how that went. It wasn't possible to run it on iOS so he told everyone that you wouldn't want to anyway. In fact, he said it was banned.
Please understand that it never existed on iOS in the first place, and its inability to run something that was quite popular was portrayed as a good thing.
Ultimately killing flash is a good thing, since nobody wants to be stuck using propietary crap, if possible.
Re: (Score:2)
Many thought it was because it would let you play games beyond the great wall of Apple. But this was often waved away as a false idea. But with the way Apple had been fighting against game streaming services, the claim about being able to play games beyond the great wall of Apple seems less farfetched then before.
Re: (Score:2)
> But there wasn't a technical limitation there.
Actually there were a several reasons [archive.org] that Steve Job's described, some bullshit, some technical, some political, and some practical reasons:
1. Adobe is not "Open" like HTML5, CSS, and Javascript.
2. Adobe claims Apple can't access "full web" due to 75% of video on the Web is Flash even though most video is available in H.264. Apple doesn't support Flash games but the App store already had 50,000+ games.
3. Reliability, security and performance reasons
4. Poor
Re: (Score:2)
HTML 5 is not a good replacement for flash.
It's a lot harder to write stuff for it, and it's not as easy to distribute.
Of course, the culture that allowed things such as newgrounds to thrive is also dead thanks to the change facebook did, but removing the tool and replacing it with something worse don't help.
Re: (Score:3)
"HTML 5 is not a good replacement for flash.
It's a lot harder to write stuff for it, and it's not as easy to distribute."
Oh, wow, no one told me today was opposite day.
Re: (Score:2)
Ten years ago, hell even in 2017, it was true. HTML5's canvas (even with 100% coverage) cannot do everything flash can graphically. And it was erratically supported. The OpenGL version isn't very easy to use to create 2D assets (like Flash primarily was) and frankly, it's 3D implementation seemed to lag even Flash's. It still might.
Ease of distribution I assume is referring to how different some browsers parse code.
Meanwhile, I still had Fortune 500 clients asking for Flash content in 2018 because they w
Re: (Score:3)
100% of platforms supported Flash at the time of Farmville's release except for mobile platforms (which at the time had a barely functioning web browser). Even Apple hadn't formally announced they won't bring Flash to mobile at the time. No lifecycle announcements had been made and HTML5 was non-existent outside of a W3C publication, certainly it wasn't used anywhere.
You have a very strange memory.
Also they milked users of their crap little browser game for nearly 12 years. They got a fucking HUGE return on
Re: (Score:3)
100% of platforms supported Flash at the time of Farmville's release except for mobile platforms
I remember running flash on Android. It wasn't supported after a while, but it totally existed and was supported back in the timeframe you're talking about. Google killed it off in late 2012.
And nothing of value was lost? (Score:2)
...per subject...
Re: (Score:2)
Wow, it's as if you've read the minds of a couple million of your fellow Slashdotters...
Good riddence! (Score:2)
My wife found it incredibly addictive, at one point I was ready to sue Zynga for estrangement of affections.
Re: (Score:2)
Re: (Score:2)
Make sure she doesn't find out about Farmville 2 or Farmville 3 all of which still work fine.
Re: (Score:2)
Set some boundaries, dude. For both of you.
Lewis Black (Score:2)
If only FarmVille had a virtual grave to piss on.
Thank you Steve Jobs (Score:4, Informative)
He wasn't the only one to decry Flash, nor the first; but he certainly got the issue out there in the mainstream.
Re: (Score:3)
Re: (Score:3)
He wasn't the only one to decry Flash, nor the first; but he certainly got the issue out there in the mainstream.
Hating flash was mainstream long before Jobs had his say on it. It was so mainstream that by the time Jobs said anything a complete functional replacement in the form of HTML5 was already ratified. The world literally solved the Flash problem before Jobs even formed an opinion on it.
Re: (Score:2)
> The world literally solved the Flash problem before
> Jobs even formed an opinion on it.
Oh? That's funny. Because no flash on iOS started in 2007... before it was even called iOS, actually. I'm not sure when Steve Jobs first personally expressed his opinion on the matter, but his famous "Thoughts on Flash" letter was in 2010. Now, by my math, both 2007 and 2010 are came before 2020. And, I don't know about you, but not being a telepath who was in close enough contact to scan Jobs, I have no idea
Re: (Score:2)
Oh? That's funny. Because no flash on iOS started in 2007... before it was even called iOS
So did no clipboard. Don't confuse iOS being an incomplete platform with Apple making a formal declaration on Flash. Steve Jobs made no formal mention of Flash support prior to 2012. The thoughts letter was just that, thoughts.
Now, by my math, both 2007 and 2010 are came before 2020.
That's cool. Who cares about 2020 since we're talking about 2009. Jobs said nothing before 2010 (by your own admission), nothing formal before 2012 on platform support, and when was HTML5 released? Oh that's right 2008.
2008 So, given that the flash problem was literally... FINALLY...
Re: Thank you Steve Jobs (Score:3)
Oh kid. Stop rewriting history.
He ONLY did it, because Flash, like Java, would have allowed people to run whatever they liked on their own damn pocket computers, and it would not have been the locked-down walled garden appliance gadget that control freak Steve Jobs wanted.
Nothing to do with anything else.
Why do you think other browser engines are still not allowed on iDevices?
Re: (Score:2)
This. Jobs wasn't a pro-security crusader, he was a user-imprisoning gatekeeper.
Re: (Score:2)
Cue up the misattributed H.L. Mencken quote (Score:2)
What, js+opengl not good enough for farmville? (Score:3, Informative)
Seriously, even my phone can run quake 3... in the browser but zynga could not port it to asmjs+opengl? It wasn't a surprise that flash was being phased out. They had all the time in the world. I suppose they made whatever money they cared for.
Re:What, js+opengl not good enough for farmville? (Score:5, Informative)
They made Farmville 2 and 3 that are html5 and mobile.
Re: (Score:2)
I think they had mobile apps as well.
The article just states that the original Facebook flash-based game will be ending and users will either have to move to other games or to a different version.
I really doubt there were many people using the original Flash version anyways.
Re: (Score:1)
Re: (Score:2)
Re: (Score:2)
Already on going check ruffle
https://ruffle.rs/ [ruffle.rs]
Re: (Score:2)
Why port when you can just re-write. Your complaint is like criticising Infinity Ward that you can't play the original Call Of Duty and are stuck playing one of the many sequels instead.
Re: (Score:2)
And the archived players (Score:2)
Does anyone know where the archived players are or how to verify them? Because adobe used to have gigs of them up and removed them from the page when they EOLed Flash.
Re: And the archived players (Score:2)
Cert CRL checking can be disabled in OpenSSL and Firefox, due to the privacy issue of it leaking your activities. .patch file to /etc/portage/patches/www-browser/firefox/. Bu AFAIK, the about:config setting is still there. (Forgot what it's called.)
Hell, in Firefox you can always patch it out and compile from source. On Gentoo, this is as simple as saving a
Re: (Score:2)
For generalized content, sure. That's good advice. However there is some white listed Flash content (some I wrote) I want to preserve access to. In some cases for the memories, in other cases in case I want to rewrite it in HTML5.
Wrong link after the caption (Score:2)
I might have seen this tech problem before... (Score:2)
The person does know the old tech through and through, but with this high level of job security and super specialization becomes and surrounds themselves with gatekeepers to make sure some new whipper-snapper doesn't c
Re: (Score:1)
Like the old guard isn't tasked with keeping the cruft running with minimal resources while the managers squeeze every last bit of profit out of it and then shut it down to replace it with something new in the name of the holy product life cycle. But of course the nerds get the blame. The bullying never ends.
Re: I might have seen this tech problem before... (Score:2)
Is this some kind of self-denial nerd-who-thinks-he-is-an-80s-sports-jock thing you got going there, mate?
Ger back to your mental hospital!
Re: (Score:2)
I gather that you're still a young whippersnapper who falls for every latest tech fad like it's avocado toast. On the whole, this just leads to companies deciding to rewrite all of their existing (and working) code for the grand new paradigm, only to discover that this creates a new set of bugs and flaws and work-arounds. It's churn for the sake of churn, and only profits the folks promoting the new fad.
Re: (Score:2)
fad like it's avocado toast
When I was a kid we called avocado toast an open faced sandwich. We paid less for it, too.
Re: (Score:2)
I gather you're a PHP hack. Hit close to the mark?
Re: (Score:2)
I did like PHP years ago as a web back end as it was certainly the best for that specific task. But the framework religious freaks took over PHP after I stopped having any use for it. Now I can't recommend against it strongl
I've seen you before (Score:5, Insightful)
I might have seen you before.
I've seen the new guys come in and say we need to throw out 20 years of work, work that forms an industry-leading product, because "it's written with old tech". Old tech like that HTML you mentioned. Something they don't mention until they are asked is that they don't know the existing tech, and therefore don't know how to work with it. They only know how to make React stuff with a particular WYSIWYG. Everything else they want to rewrite in a new programming language, a language that is nearing it's 1.0 release. They're pretty confident that the language will develop to actually be functional by the time we need each language feature that doesn't yet exist. Here's one example:
The new hires really wanted to play with AWS Lambda. Because it's new and highly scalable, they said. In every meeting, no matter the topic, their solution was always "rewrite it as a lamda". AWS Lambda is an interesting thing that could be useful for certain tasks but unfortunately the new crew couldn't quite understand what Lambda *is*, what kinds of tasks it's designed for. For those unfamiliar, AWS Lambda is a "function as a service". You write a function, maybe 6-24 lines of code, and that becomes a web service. It's useful for translating input in a given format to another format, something like PDF to text or Excel spreadsheet to csv. Any kind of input to output translation. The name Lambda comes from math, where a lambda is a true function which accepts exactly one argument and returns exact one value, something like square-root. AWS limits the number of seconds that a lambda can run and limits the input because a lambda is a function, not an application server.
Their problem, they thought, was how many hacks they needed to use to get around the time and space limitations so they could run very large applications, hundreds of thousands of lines of code with multiple databases and a thousand inputs, as a lambda. Every meeting they' want to rewrite tens of thousands of lines as a lambda, and every meeting I'd shut them down insisting that they a) spend 10 minutes finding out what lambda is first and b) choose one of the 100 or so items from our to-do list, accomplish something that actually needs to be done, rather than throwing out perfectly working functionality and replacing it with a new buggy version.
Eventually I got tired of the same thing over and over, so when they came saying we should throw out a particular software and rewrite it as a lampda I didn't say much. I did tell them it wasn't a good fit, I'd rather they tackle one of the to-do list items as a lambda so we'd actually be moving FORWARD, but I didn't totally shut them down. I did know that the functionality they intended to replace was tricky, probably a level or two above their ability to get it right.
What they wanted to throw out and replace was some code that runs on patch Tuesday every month, parsing information about which patches cover which vulnerabilities. That's tricky only because of supersedence and the need for the output to be efficient. The June roll-up covers all of the vulnerabilities that were covered by May, which covers all the April ones, etc. This backward coverage isn't expressed in the monthly data fees because it would make the data feed thousands of times larger. Also, they wanted to do a couple other very similar services which get patch and vulnerability information from other sources once a month or once a week.
Since I didn't shut them down, they got a meeting to present a quick summary their proposal to our boss's boss. I sat in and stayed quiet. That led to a meeting with the grand-grand-boss, the big guy. I sat quietly while they espoused the virtues of AWS Lambda for 15 minutes, mostly just saying "scalable" over and over. Lambda could do the job 5,000 times per minute!, they said. I silently chuckled to myself.
At th end of their presentation, they asked if there are any questions. I had three short questions:
Me: "This is to replace the Patch Tues
Re: (Score:2)
Executive summary: confessions of a cancer.
Re: (Score:2)
Re: (Score:2)
From what you have described you are 20 years out of date, probably
Re: (Score:2)
> New features take super senior programmers
Yes, it requires people who know how to actually develop code, not just press buttons in a shiny WYSIWYG.
> It is surrounded by procedures such as writing documentation
Oh I'm sure that *your* code has to be thrown out and rewritten every year or two since you don't document any of your design or any of your changes, so nobody knows how it's supposed to work. No argument there!
We document https://httpd.apache.org/docs/... [apache.org] how it works, so when you need to add
Re: I've seen you before (Score:2)
The 'new guys', the 'new hires'? Kind of vague. Come out and say it. They were diversity hires weren't they?
Re: (Score:2)
Actually the new hires were simply newbies, less-experienced programmers. Cheap programmers.
The "diversity hire" actually turned out to be quite good. I don't know that that had anything to do with my calling the boss out on illegal discrimination. When he said "I'm posting a new position and I'm going to hire a woman this time", I let him know what he had just said is actually illegal. I advised him that what he can do legally is advertise the position via channels that may make it visible to qualified wom
Re: (Score:2)
None of that really applies here. Instead of updating Farmville for HTML5, Zynga just moved to mobile for Farmville 2 and HTML5 for Farmville 3.
Re: (Score:2)
Now the RubyOnRails popularity has waned, Ruby programming has gone back to what it was before; mostly unix, and one of the biggest pluses is that it has a really-low-level, very simple C api. And the Ruby stdlib follows the conventions (and warts) of the C stdlib.
Re: (Score:2)
You totally nailed that right down to the details. This can only mean that you have seen both scenarios, one where the old cancer wins (supposedly, since they only succeeded in wrecking things which might also wreck their meal ticket in the long run) and another where the cancer was successfully forestalled. Personally, I have only directly witnessed the former, and that a number of times, always coupled with both sides losing in the end.
Re: (Score:2)
This only works if they can keep the old cancer from infiltrating the new company and then becoming its project/product/engineering managers.
Personally, if I was hired to fix an old guar
Lost History (Score:2)
I, for one, am mourning the loss of Flash as it means thousands of web games (not just Farmville) from the web's first couple decades will now become largely unplayable and potentially lost forever. Yet I haven't seen this huge loss decried once in the media, anywhere.
The Internet Archive [archive.org] is trying to rectify the situation working with the Ruffle emulation project- although it's still far from full fidelity and the number of games the Archive has currently is but a tiny fraction of those that existed on the
Re: (Score:2)
Yet I haven't seen this huge loss decried once in the media, anywhere.
That is because nothing of value was lost. And this is probably the one time this can legitimately be said without being funny.
Not everything in history is worth preserving. In fact Flash should be archived on a single page with only the text "Please don't do this shit again!".
Re: Lost History (Score:2)
Uum, if you think nothing of value was ever implemented in Flash, you definitely have never seen Kongregate.
Flash was just a simple authoring tool for animations. Nothing wrong with that per se. HTML5 is not much different from that. And if you think the vast majority of Flash content was useless crap, I recommend you try old 90s Geocities homepages written in HTML for comparison.
It only died because 1. it was full of security holes, and 2. and most importantly, HTML5 webapps IS the new Flash.
Now just wait
Re: (Score:2)
Look up Flashpoint:
https://bluemaxima.org/flashpo... [bluemaxima.org]
Re: (Score:2)
You can also just use open source flash developer tools to play them locally.
Preserving Flash-based games (Score:2)
So what is the long-term plan for preserving Flash-based games? While most people know Flash as a browser plug-in, there's actually a lot of engines that execute Flash. Lots of AAA games used it for their UI overlays, loading screens, etc. I can't remember the names though. Are those engines still around? Can they be used in a project like MAME?
While writing this I found Flashpoint [bluemaxima.org] but I am not sure how far along they are or what Flash games it works with.
Re: (Score:2)
Re: Preserving Flash-based games (Score:2)
I know Doom 3's UI interface is Flash, for example.
Not to worry, you can still play Cow Clicker (Score:2)
http://cowclicker.com/ [cowclicker.com]
Perfect game for 2020 (Score:2)
With everybody sitting around at home with nothing to do, what could be better than a game where you repeat the same mindless clicks over and over?
Flash still working for me on FF-ESR (Score:2)
Thats one of the advantages of the ESR (and on Mac, to boot).
Granted, by next ESR release (around Aug 2021), the NPAPI plumbing will be removed, and flash will stop working. But I get my 6 months of reprive while the WebSite Laggards get their act together.
Another of the benefits of using the ESR...
For what is worth, if you are a corporate, Adobe offloaded support for flash to Harman (a subsidiary of Samsung):
https://services.harman.com/ [harman.com]
This is standard fare in the industry. By the tail end of Symbian regin
Wasn't it just a Stardew Valley clone? (Score:2)
A shitty one.
Yahtzee from Zero Punctuation made me believe that, though I obviously never played either game.
If only! (Score:2)
Re: (Score:2)
Who will water my crops? (Score:1)
Re:Adobe's "Decision" (Score:4, Insightful)
Flash was and is a steaming pile of shit. Google may have nefarious aims, but that doesn't negate the fact that the end of flash is a very very good thing.
Re: (Score:2)
Flash was and is a steaming pile of shit. Google may have nefarious aims, but that doesn't negate the fact that the end of flash is a very very good thing.
Flash served a purpose and grew big for a reason. It had nice development tools (compared to other ways of getting interactivity and motion), and it largely avoided the hell that was cross browser development of anything complex.
Yes, its time has passed, but it had its time for real reasons.
Re: Adobe's "Decision" (Score:2)
And it differs from the "HTML5 platform" ... where?
In having even more attack surface?
Flash *wished* it had full GPU access like WebGL.
Just wait. The bugs to make the analogy complee will start coming, as soon as Chrome comes to the last part of the IE6 lifecycle: Abandonment due to monopoly.
Re: (Score:2)
Re: Adobe's "Decision" (Score:2, Informative)
Uhh no. It was Apple. They famously refused to support it on the iPhone and then everyone jumped on the bandwagon. Android didnâ(TM)t even exist at the time, so nobody wanted to waste time making Flash apps if they wouldnâ(TM)t work on one of the best selling smartphones.
Re: (Score:3)
When Jobs made his announcement about Flash, Android did indeed exist. I had an Android phone that did Flash. Slow and buggy but it existed on Android.
Re: (Score:2)
Are you talking about when he wrote that open letter? But even before that .. since it came out the iPhone didn't support Flash.
Re: (Score:2)
Re: Adobe's "Decision" (Score:2)
Then iBrainwashing is strong in this one...
What if I told you that Apple didn't even make the first smartphone. Nokia's Epoc/Symbian-based series did that. And they had a freaking file manager too!
Apple only made the first condescendingphone. And the first that was useless for doing real work. (No scripting, no terminal, fuck-all in total.)
With no 3G and no camera, in case iDeciples ever forget.
Re: (Score:3)
Was there any phone before the iPhone in which you could go to a web page and scroll it by flicking your finger? Nope. Apple made the first capacitative touchscreen phone with a finger friendly UI.
All the other smartphones were scrolled by pressing buttons. The iPhone also had the largest display.
Before the iPhone came out in 2007, I made this post in 2005 about how all smartphones suck: https://hardware.slashdot.org/... [slashdot.org]
Other commenters on that article on slashdot were saying smartphones would never work p
Re: (Score:2)
In 2009, 50% of smartphone internet traffic was iPhone and it had a tremendous marketshare growth rate. https://techcrunch.com/2009/03... [techcrunch.com] and it was of course very influential in ending Flash.
Re: (Score:2)
Re: (Score:2)
No it really was Adobe's decision. One can argue that it was Apple or Google, or whatever.
But in reality, it is mostly a result of Adobe not giving a shit. Flash used to be good, and it took decades for web standards and browsers to catch up. Adobe could have decided to fix their bugs, optimize, improve accessibility, etc... They could actually have worked making it a standard part of the web. They didn't. Instead, when Flash dominance started being challenged, they jumped on the HTML5 bandwagon and let Fla
Re: (Score:2)