On July 11th, we had our second Repl.it IRL and it was an amazing event!
On July 11th, we had our second Repl.it IRL and it was an amazing event!
As you use Repl.it more and more, you often find yourself frequently creating repls for quick testing. On your repls dashboard, you can mark important repls by starring them - allowing you to quickly access them. However, there was no way to surface your best work on your profile - users would have to sift through all your repls to find the one they were looking for - until now.
At Repl.it our goal is to provide state of the art in developer tools to everyone in the world, for free. When we started moving our product beyond a simple REPL and started adding IDE features, we had to invent standards and wrappers around every language tool for our frontend to consume. For every editor feature, say errors and warnings (linting), we had to extend our development protocol with a set of commands and data structures, and then teach our development containers how to wrap the given tool, say Pylint, and our frontend on how to consume it (say annotate the editor with errors and warnings). A similar thing has been happening with IDEs for the past few decades -- every editor had to come up with their in-house ad-hoc protocol, and every tool developer had to build adapters and wrappers for editors to consume.
I’m still in high school but I just flew from San Francisco to New York City to be a sponsor at a high school hackathon so, yeah, you already know that the whole experience was pretty awesome.
For the month of July, our Repl.it IRL will be taking place on July 11th from 4 to 7 PM at the Bradfield School of Computer Science!
We recently added some changes to how eval mode/project mode operates. These changes allow you to interact with generated files through the console.
Two days ago we introduced our beta support for React frameworks, ranging from static-site generators like GatsbyJS, to fullstack frameworks like Next.js. Today we're launching a significant performance enhancement that we're calling preboot.
On Monday, June 11th, we had our first Repl.it Meetup and it was super awesome!
Most systems -- both natural and artificial -- decay, rot, and eventually die. Software is no different. A lot has been written about fighting "software rot" but there's another type of rot related to software that's not talked about much -- the development environment rot.
Ollie Parish, also known as @op on Repl.it, is an avid Repler and constantly pushes our systems to its limits (in the best way). In this guest blog post, he describes his journey in using neural networks to generate large primes. You can also check out the repl described in his research: https://repl.it/@op/DNN-3-1
Along with the ability to star repls and tag repls, we now take repl organization one step further with the ability to search through your repls.
At Repl.it we come to work every day to explore a single idea—what if programming just worked? What if instead of fiddling around with packages, configurations, and mismatching versions, you just open your IDE and start coding. What if developers can go from an idea to coding and shipping software with no time in between. What if teachers who want to teach programming don't have to also work as IT administrators. What if students can just code their homework without having to set up the development environment on every computer they wanted to code on.
Repl.it is becoming the platform where developers come to learn and build. With web hosting we also made it possible to host websites and since then we've seen an explosion of websites hosted on Repl.it. Today we're going further by making it possible to deploy servers on Repl.it.
Sometime in 2016 we in introduced the concept of "files" to Repl.it, you would click add file and a tab would appear on your Repl. As simple repls grew into full fledged applications and websites tabs started getting ugly and hard to manage.
As we released I Built This, our community where users can post about their repl creations, we were exposed to many amazing projects created by our users. To kick it off, we hosted a competition where users post their work and garner upvotes for prizes. The projects shared in the competition spanned a wide range of skill levels, from beginner to advanced, from simple to complex.
Ever since we introduced third-party package support for Python we've seen an explosion of exciting programs on Repl.it. Everything from games to machine-learning applications that just weren't possible before.
People use Repl.it in a variety of ways; some use it for building and shipping applications, while others use it for working on homework, and many others use it as a quick prototyping/experimentation tool. Supporting all these use cases (and more) is something we care a lot about, but up until now there wasn't an easy way to, for example, quickly go back to a project that you continue to work on every day.
At Repl.it our mission is to make programming more accessible, which means our coding environment needs to be lightweight, load fast, and work from anywhere in the world. However, as with so many software projects that evolve with time, we accumulated some bloat (luckily, we haven't included a mail client yet) and quite a few ad-hoc hacks to glue everything together. In this post, we'll go over how we designed our new IDE to have a small core (everything is a plugin), to be easily customizable (even on the fly), and to server-render.
At Repl.it our mission is to make programming more accessible. We want to build the platform that will empower the next billion programmers to build the future of software. To accomplish this we needed to build a sustainable business that allows us to grow with our users.
Repl.it is quickly becoming a tool that's used in everyday programming, and our users are building all sorts of amazing programs. One thing that's been missing for a long time is the ability to access the internet from repls. Being able to call APIs or remote servers is something programmers can't live without. That's why we're excited to announce that starting now we're openning internet access for all!
You can now copy and clone an assignment from one classroom to another! Many teachers have requested this feature, and we are happy to announce that it has been released!
At Repl.it our mission is to make programming more accessible. We can’t do this alone so it’s great to partner with non-profits and hack clubs that share our mission. Re-coded is one of those non-profits, they're teaching programming in the refugee camps in Iraq and Turkey. Today I’d like to share with you their story of how they found Repl.it useful in overcoming logistical challenges.
People in our community build awesome games, apps, and websites on Repl.it's web programming environment, but until now they didn't have any easy way of sharing these creations with other people.
At Repl.it we focus on simplicity, speed, and, most importantly, reliability. If you're using Repl.it as your primary or secondary IDE we want you to be confident that the time you invest working on your code will never go to waste.
We are always excited about launching new features and sharing with you, our dear users, what we’ve been up to. For the past few months, Amjad, Mason and I have been working hard and last night we quietly launched the new repl features. These features required a lot of infrastructure and data changes which is always tricky to execute. We ran into some technical difficulties last night with the data migration but was able to bring the site back up and things have been running relatively smoothly since then.
We strive to make the workspace as useful as possible while keeping it intuitive and approachable. We get a crazy number of requests for features every day, not to mention our own ideas. It becomes a challenging balance between feature creep and simplicity. Lately we've added a few of these features that we hope you'll find useful and, if not, you won't even notice they're there.
Like any other startup, we go through ups and downs. However, we try to keep a positive energy, and you, my friends, contribute to that by sending your love, support, and thanks everyday. Above all, you inspire us with stories of how our product helped you learn, teach, and even develop a new skill to land a better job.
We're constantly surprised and delighted by the creativity of people in our community. Whether it be games, animations, utilities, or simply snippets to answer Stackoverflow questions -- it's always fascinating to see! However, we haven't done a good job giving credits to authors for their creations.
Debugging web projects on Repl.it can be frustrating. Until today, there was no easy way to view your errors and console logs (unless you open your browsers' developer tools). But that's changing because we're introducing our new tabbed console view for environments that has graphics output (like Web and Python Turtle).
Some changes and fixes we make don't deserve their own blogpost. So we thought a good way to keep you up-to-date is to collect however many that could be of interest and write a "Changelog".
The label "sessions" is very near and dear to my heart. I vividly remember how Amjad came up with the name and why. After we learned that people would like to create accounts on Repl.it, we were trying to figure out what was the main value proposition for creating an account. Of course, it was saving code! But what do you call a list of code projects saved on your account?
At Replit, we're always looking to give you new ways to learn and build cool new things, so we partnered with our friends at Expo to create a React Native environment. Expo is an amazing technology allows you to develop apps on your phone without downloading any IDEs or simulators. All you have to do is get the Expo App on your phone and use it to connect your phone to Replit.
There is a special moment in learning: when a student runs their code against the unit tests and finally sees all of them turn green. This moment of enlightenment means the student has just managed to create their own working solution to a difficult problem, and has made a step towards becoming a great programmer! Wouldn't it be cool to further enhance the student's knowledge by showing the student different approaches to tackle the same problem?
Last year we introduced support for importing any Python package from PyPi and -- although we don't have perfect support for all packages -- it turned out to be a very popular feature. That's why today we're excited to continue the roll-out for the rest of our platform starting with web-based languages.
Software development is one of the first -- if not the first -- examples of what J. C. Licklider called the Man-Computer Symbiosis. A "cooperative interaction" between people and computers where the person is concerned in what may be classified as the creative aspect of the work such as setting the goals, formulating the hypothesis and evaluating the results while the computer does all the "routinizable work".
We've been seeing more and more coding video tutorials using YouTube and Twitch.tv. Today we're sharing some of our favorite YouTube videos that uses Repl.it
Earlier this week we introduced Haskell support. And now, as promised, we're continuing to add more functional languages. So today we're excited to introduce Clojure. A Lisp dialect that runs on top of the Java Virtual Machine with a focus on immutability.
We heard your requests for Haskell and today we're excited to finally announce Haskell as yet another language we support. We've decided to put our focus on adding more functional languages, starting with Haskell, so you can expect more very soon.
Hey teachers, we've noticed that you have been teaching up a storm in your Replit classrooms, and with this feature we want to turn those storms into educational hurricanes! To do so, we implemented teacher collaboration, which allows you to add an additional teacher to your Replit classrooms. This additional teacher can do almost everything you can do, excluding a couple of small destructive things...
Fundementally, learning is about completing basic material before moving on to more advanced stuff.
At Repl.it we aim to make the full power of programming easily accessible for everyone. That's why when we designed our code execution service we decided that we would not timebox users' programs or sessions.
At Repl.it our mission is to make programming more accessible, and the best way we found to achieve this is to support, you, the teachers on the ground doing working with students. That's why we want to make sure you control the student experience and today we're making it possible to control the assignments order from your classroom dashboard.
Today we're excited to release a feature which shows any files your program creates directly inside the REPL. And any time that file changes it will be updated live in the editor. This can be anything from a text file to a gif.
We recently made it possible to import any package from PyPi. However, people who missed the announcement didn't know this was possible. There was also no good way to search and explore packages.
At Repl.it, our goal is to make programming more accessible, and as part of this we aim to provide the full power of popular programming environments with no setup time. And I don't think it's an understatement to say that debugging is the majority of what we, as programmers, do.
Today, we're excited to introduce lint support for Python3. Where previously you had to run your code, look at the console for an error, find the line number of the error and then find that line in your editor. Now, we'll show you errors and potential mistakes live as you type!
At Repl.it, our goal is to make programming more accessible, and as part of this we aim to provide the full power of popular programming environments with no setup time. And no modern programming language is complete without third-party packages.
On Wednesday we announced assignment scheduling, and today we're releasing another date related feature—due dates. It's no secret that students can procrastinate, so sometimes it's useful to have deadlines for the assignments as a reminder.
Today, we're introducing scheduled assignments. Teachers using Repl.it Classroom can now schedule assignments to be published in the future. You can imagine working on your assignment, schedule a publish date, go on vacation, and still have your students receive their assignments at the right time.
Simple design is not only how the product looks like, but more importantly, how the product functions; it’s about creating the easiest and simplest path for the user to accomplish their goal. Usually, simple design comes from complex requirements and a lot of ideas — in order to break it down I usually go through a process that I call Vagueness to Clarity
It's no secret we're big fans of REPLs. We believe that immediate access to the programming environment accelerates learning and is generally more productive. REPLs cut out the middleman -- no need to build UIs or scripts for every possible action you might want to take -- just talk to the interpreter directly.
Arguments over programming language semantics, standard library behavior, or syntax can now be simply and immediately settled within the chatroom by talking to Evalbot. It is a bot that can speak over 10 programming languages and is ever-present on Messenger and can be added to your team chat on Slack.
Before we decided to build repl.it classroom, we paid a visit to one of the schools using us in the classroom. I felt excited and anxious at the same time; I was introduced to the teacher and students in the class, and then my job started as designer observing and paying attention to every single detail.
Rate limiting is standard practice for services offering an API. It's used for both protecting against bad actors, for example, attempting DOS attacks and to simply enforce limits on the service. There are many resources on the web on how to implement a rate limiter in your favorite language/stack. However, I couldn't find anything on how to rate limit Websocket connections (they differ in that they are persistent connections).
Repl.it's code execution API is an HTTP and WebSocket endpoint that you connect to and send code to execute. You can connect from any device or browser and start executing code. This guide will describe the concepts behind the service, how it can be used, and provide a step-by-step guide for signing up and trying out the service!
Autocomplete plays a big role in how we use software, imagine a world where you have to type full search terms without predictions into google search, ugh, the savagery! Many developers employ this technology when writing code in order to increase their productivity. So we decided to implement this feature to help you become the power user you want to be.
In this age of containers it's much easier to run arbitrary code in the cloud. The harder parts are scaling the service, making it reliable, and —as in this case— creating cool and useful experiences. When we looked at existing Swift REPL implementations on the web we found that none delivered a stateful and interactive environment. Just an editor with a run button.
We're excited to launch this new part of our site.