This is a huge @Glitch update: You can build & launch a full-stack or static site, using frameworks like React or Eleventy, in *under a minute* — for FREE. It's now faster to build a real, coded website on Glitch than with a no-code tool. See for yourself: glitch.com/create-project
There are many massive improvements to go with the huge speed boost. New starter apps handle annoying configuration & build scripts for static or full-stack sites. Better syntax highlighting. And you can instantly add a domain to your new app. (Use that old domain you've got!)
Full details are here: blog.glitch.com/post/remix-a-w… The entire web is better when it's made by regular people using open tools, instead of on proprietary platforms with creepy algorithms. Go launch that site you've been meaning to make, right from your browser.
A massive thanks to all the communities around tools like @reactjs, @eleven_ty, @vite_js and @fastifyjs — we wanted it to be as easy for developers to use these powerful, open platforms as it is to use one of the site-building tools you hear advertised on a podcast. Now, it is.
Thoughtful, well-argued reflection on software licensing. It's long been evident that the "software freedom" battlegrounds defined in the 70s/80s are often anachronistic at best, and also obvious that "free" licenses can be abused as a tactic for open-washing harmful actions.
These shortcomings are a big part of the reasons we make apps remixable by default on @Glitch. Building a community with norms of reuse & sharing is far more powerful than any software license can ever be. Behavior & expectations matter more than any legal language.
And making it normal for everyone to create the apps they need (and the web they want) instead of relying solely on services that surveil them, or systems that keep their data captive, does more to advance actual control and "freedom" for people than any abstract license can.
This is something pretty fantastic: The @StackOverflow team has made a free, full-featured version of Stack Overflow that you can run for any team of up to 50 people. stackoverflow.blog/2021/03/17/sta…
Chat apps are great for conversation, but this is perfect for having answers that anyone can reference when they need. Stack Overflow for Teams even plugs into Slack or MS Teams, which means no more searching back through an endless chat archive to find an answer to something.
On a personal note, I'm really happy to see the @StackOverflow team deliver this for everyone because it goes to one of the most consistent things people have asked me about over the years: How can we have a version of SO where everyone feels safe & welcome to ask questions?
Interesting to see the reactions to the phrase "bamboo ceiling" in this headline; the term only even came to popularity about 15 years ago, but norms have shifted quickly enough that it seems off-putting rather than inclusive. (Also likely picked by an editor, not the writer.)
Ah! Was picked by the writer of the piece, in reference to @JaneHyun's work. (There's long been discussion about the appropriateness of "bamboo" in reference to e.g. South Asian cultures.)
Anyway, I'm heartened by how many non-Asian-American folks responded with curiosity or skepticism about whether that phrasing was respectful, and especially by how many incredible AA films, actors & artists are being recognized for their work.
Ahhhh omg it feels so validating to hear this has a name! I really struggle with talking over people (I understand many experience this very negatively) but it’s an incredibly difficult pattern to change because it’s literally how I grew up communicating enthusiasm & support.
Not talking “with” someone is like leaving them alone, similar to refusing to look at them when talking.
It’s interesting (and probably telling) that so much of the traditional business literature talks about communication styles, but much of it is grounded in what feels like a very narrow Ivy League conception of communication. This is so much richer. thoughtco.com/cooperative-ov…
Attempting a (necessarily imperfect) simple explanation: most coders reuse code from others in the course of doing their work, either public code on the web or private code from their coworkers/colleagues…
A lot of times, you can figure out the names of the private code libraries being shared within big organizations. On one of the most popular tools, if you made a public library with the same name & said it was a newer version, those coders would unknowingly get your code instead.