He's in everyone's good graces because he's now known as a kookie old man from the MTV show _The Osbournes_ that aired in the mid-2000's. Same reason why Michael Jackson, arguably the most famous person of the 90s, isn't as popular after his death given his reclusiveness and scandals. We tend to remember stars for the last impact that they had — not what they started off with.
Not super great of them to release an original movie so close to Lilo and Stitch, which is still in theaters and just crossed $900M world-wide. And of course, How to Train Your Dragon, as mentioned in the article.
Yeah I saw that but they never said where those calories were coming from, which could be a few different sources. Sugar seems like the most obvious but calories could be talking about milks or creamers too.
I consider frames to be an example of MFE, actually. I believe I remember reading that Spotify (long ago) used frames in their app so each team could be self-contained.
Edit: In fact, I'm pretty sure Geers' book associated with that site says as much.
> For most people Python/Javascript also does the job
True, and people should use whatever works best for them/for the job, no questions asked.
But they also have nowhere near the same experience even though they technically have REPLs. The way a JS/Python dev typically use a REPL is experiment in the REPL itself, then when happy, write the "real code", while a Clojure developers write "real code" all the code, sending selections of code to a REPL in the background, viewing the results in their editor, and just saves the file when they're happy. It might sound similar, but very different experience.
> However, learning a Lisp also makes you a better coder because of immutability and less side-effects. Hence why Clojure is still around.
I don't think "immutability" and "less side-effects" is something lisps in general/all lisps promote/facilitate, it's mostly a thing that Clojure (and children) sticks out for caring a lot about. Scheme/Common Lisp is about as immutable as JavaScript is, and lots of CL programs/code out there spreading mutation all over the place, while in Clojure it's pretty common to just have small "pieces" of mutation in somewhat centralized location.
It can do, but it also can make you a worse coder. Specifically in typed languages.
One of the issues I've ran into with Clojure devs doing Java is that instead of relying on a type, they tend to want to write stuff like `Map<String, Map<String, Object>>`. Even when the key sets in both maps are well known.
This becomes worse when you mix that with Immutability. Immutability can be fine except when you need a mutation. In applications that require heavy mutation of data a `Map<String, Map<String, Object>>` is one of the worst ways to represent structured data, copying that structure is EXTREMELY expensive.
This isn't to say that you shouldn't usually strongly prefer Immutability. But it's also to say you shouldn't underestimate the cost of allocations and copying data.
Theres always tradeoffs. Part of being a good programmer is knowing when those tradeoffs are best applied.
I think it's "around" because it's quite productive and sits on a rock-solid runtime with support for an astonishing amount of libraries.
Around these parts it's common to have read and appreciated Paul Graham's old writings about becoming a better software developer through Lisp, and that would be Common Lisp, i.e. very mutable, commonly object oriented.
The proper context, too, is that Liz Lemon is in charge of showrunning a Saturday Night skit show and is facing many challenges. "Lemon, it's Wednesday" implies that there are many things that can go wrong in between Wednesday and Saturday.
It looks like ads generally are posts from business accounts that then get a sponsored badge and some promotion among feeds. From a fediverse perspective, you won't see them unless you follow the pizza hut threads feed (to use a random example.)
