It's true that certain blocks still use YUI, but this is system functionality that's not part of our public API. In new templates, a Squarespace developer won't see or touch YUI code.
We're no longer creating new features with YUI. We write new frontend editor functionality with modern libraries like React.
> Why would a developer want to see a cached version of a page?
Squarespace is a CMS. There's an online content editor where users can add text and images. The content is rendered using a template which contains the HTML/CSS/Template code that defines the layout for the content. The squarespace dev server makes it easier for the developer to work on the template code using content from the live site. I don't think you'd run into a situation where it looked fine locally but broke in production, because the content will be the same.
> why not just make it a portable executable for each platform
NPM has great cross-platform support, and it's used by lots of web developers. That's why we chose NPM. It allowed us to build a cross-platform tool without having to maintain lots of separate installers for various platforms.
Also we wanted to take advantage of the same java based template and less compilers that we use in production (that are open source), which is a large part of why we used java. I'll admit it's not a natural choice for an NPM package, but it's working well for us so far.
Cool tech, fun toy! I hope it is successful. I think Joel should focus on it's toy-like nature, and potential as a learning tool, rather than trying to build this into a production grade tool.
I spent years building tools for this market between professional devs and non-developers. (Backlift.com and then Brace.io) It's really tough. Most people learning to code are trying to gain transferrable skills that can help them land a job. For them, learning git is a fruitful tangent along the path to shipping. Those that aren't interested in building those transferrable skills probably don't self-identify as developers. Making developer tools for non-developers is tough.
Hi, I'm one of the creators of Brace Forms. I am really happy with the way formspree is working on assembly.
Want to send feedback? There's a form at the bottom of formspree.io and we've got people in the community that are now responding to those customer service inquiries.
Several have asked about the 10m delays. We switched email providers so we could improve our email deliverability and spam filtering. But the new provider is throttling us while they get a sense of our email traffic. I've been told that it should be back to normal soon. These are growing pains.
Frankly I'm pleasantly surprised to see the project gaining momentum. The alternative would have been to shut it down.
Instead of "redirect the root domain to the www subdomain using a DNS CNAME record" it should say "... using domain forwarding".
Most DNS hosts offer some mechanism for forwarding traffic from your apex domain to the www subdomain using a 301 (permanent) redirect. Then the www subdomain can be configured with a CNAME record.
Cole with Brace here (http://brace.io). We recommend redirecting the apex domain to a "www" subdomain. Note that even using apex CNAME records (Alias records) are still a new idea, and depending on the implementation may reduce reliability or performance. (https://iwantmyname.com/blog/2014/01/why-alias-type-records-...)
Here are a few resources from our blog that explain the www redirect approach:
Brilliant work guys. Choice of initial features seems right on for a developer focused hosting service. At first I was a bit confused by the SSL offering for custom domains, until I saw that firebase actually acquires the cert and configures it. That's a huge pain point, bravo.
After receiving several emails protesting the removal of the article, I reposted it after editing out the parts that attempted to draw conclusions. There's also a disclaimer at the top that warns about the danger of FMT.
I pulled all the language that attempted to draw conclusions. I had removed the entire article but I received several emails from people who weren't interested in my results, just wanted to know what I did.
OP: Sorry all. I had hoped to raise awareness and encourage discussion, but I think there's a bigger danger that the way I presented this "experiment" will do more harm than good for the perception of FMT and at home microbiome exploration. I will consider revisiting once I've got my ducks in a row.
OP: Thanks, removed the word "significant". I can't make any claims about the results yet. The donor sample is coming in soon so I will be able to make that comparison.
OP here: It's true I'm not a doctor or scientist. This isn't a rigorously designed experiment. Yes, I am hoping that the results are positive, but I don't have unrealistic expectations. Mostly I'm just interested in seeing what I can learn about myself.
Also not much "shoving" was involved. I'll do another post later that describes the process. It's pretty gross, but mostly due to the preparation. (I had to put shit in a blender and press the button) The actual administration is about as gross as using a suppository.
I agree, and I don't intend to encourage people to be casual about the risks involved. But I'm also concerned about the possibility that this incredible tool will become inaccessible.