gchp

Came here to write almost exactly this!

I've been thinking for a while now about building a system like this. There is one particular set of traffic lights on my commute which causes 45-60 minute delays at peak times. I've wondered how some small changes to timings of the light might reduce some of that, and was thinking about building something to simulate it and test my theory.

The other thing that is interesting about traffic patterns is how truly connected the entire network of roads are. You can have a collision on a major road which has a big impact on roads several miles away. I've always thought it would be fun to visualize that somehow, to determine not just the immediate effects of a change to a road system, but how it effects other commuter routes.

Definitely going to play around with this. Kudos to the author.

An open source alternative I've used in the past is Askbot: https://askbot.com/

It's built on Django, and covers all of the standard Q&A features that I've needed to use.

I did not realise GCC supported Go until reading these release notes. What advantage/reason would I have for using GCC over the standard Go compiler?

Link to the release notes: https://gcc.gnu.org/gcc-8/changes.html

While I also find the surge of electron-based application somewhat amusing, you can't deny that it has made it easier for more developers to develop cross-platform applications without having to develop and manage several codebases with different languages.

I'm working on a side-project at the moment, a large part of which is a desktop application. Using electron allows me to get a cross-platform app out the door pretty quickly. If I had a team of more than one, perhaps I would consider using something else, but as long as it is just me electron just makes sense.

IThat's cool, didn't realise it was the same author.

I understand. The other side of that coin though I guess is that knowing this might give some more confidence in using diesel. ActiveRecord was the first ORM I used, and knowing now that diesel is "from the same stock" (for want of a better phrase) gives some extra confidence in what it can do / where it is going.

Not that I was not confident in it before...

even though it's authored by the maintainer of one of the most massively popular ORMs ever

Just curious, what ORM is that?

Yeah I think at the start there is a lot of value in just starting, perhaps without even finishing. It's that stage of just getting over the first hurdle and getting into it.

That's fine for a while but then as you say you get to the place where you have to finish. I think this can be almost as big of a hurdle as starting as it can involve a whole host of new challenges, some of which you've mentioned above.

Finishing is also, in my opinion, typically not as exciting. You've likely already solved all the intersting problems and are left with the "lesser" tasks involved in getting it over the line. This is something I've been learning myself over the past year or two.

Totally agree. What I've found too is that once you actually start and get /something/ down on the page (or whatever the medium) you actually find yourself getting into a bit of a productivity flow. It might start off bad, but I find I quickly slip into actually getting stuff done once I get over that initial paralysis.

What's your advice for indie hackers who are just starting out?

Honestly my single piece of advice would probably be to stop looking for so much advice. Shut the fuck up and go and build something.

I like this. I see a lot of people, and I fall victim to this myself, over analysing the best way to do X, rather than just trying it and learing / adapting as you go. I think there is some value in figuring things out up front, but not at the cost of never taking the plunge.

Haven't they always been charging for snapshots? My understanding is that this is a change to pricing, not introduction of charges.

I seem to remember something like and additional $1 per month on the smallest VM.

Yeah! I was surprised by the amount. When I read things now about compiler speed, I'm looking through a different lens now that I have an idea of the sheer amount of work it's doing. Pretty impressive.

I'm curious how someone made this outlandish claim sound plausible.

From the article:

Soviet television had, up to that point, been regarded by its audience as conservative in style and content. As a result, a large number of Soviet citizens (one estimate puts the number at 11,250,000 audience members) took the deadpan "interview" at face value, in spite of the absurd claims presented.

I guess this had something to do with it? If people were used to TV being a certain way, and this "interview" was presented in the same way, then it would seem reasonable that it would be taken up in the same was as every other. Nothing (aside from content) made it stand out from other shows.

Saying that, the claim is crazy, and it does seem strange that it was seemingly accepted as truth. I wonder how a similar stunt could be attempted today, and what the reaction would be...

I don't disagree, but curious - is Santa Claus considered religion?

Before reading your comment I still thought it said Sicily. My brain just assumed that was what it said

This is great!

Something I'd love to see is an overview of what parts of the source tree are responsible for what. As a new contributor to projects, that's the part I find takes the longest. Figuring out what modules do the things that I want to work on.

The guts of servo seems to be the the "components" directory. Is there a place that gives some information on each of the components in there?

Cool, looks nice!

Not related to the app, but the website. The main text above the app store buttons is really difficult to read, the contrast is quite low. Perhaps darken the text a little?

Nice work!

Well, shit. Finally I feel justified for never (read: rarely) using the "Save password", feature in my web browser.

Does anyone know if Apple have done anything towards resolving this in the 6 month window they requested? Slightly worrying now that this has been published without a fix from Apple. I don't really download apps very often on my Mac, but probably won't for sure now until I know this has been resolved. Annoying.

I used to love the X1, but recently Dell's XPS 13 developer edition as been centre of my attention

Relatively similar specs, great screen, and less expensive!

http://www.dell.com/ie/business/p/xps-13-linux/pd

I read this as "finally released" :D

Do you have syntax highlighting on? I've seen huge speed-ups with large files when the editor doesn't have to try parse & highlight everything.

I agree that its annoying though. I've started writing my own text editor, and aim to solve this problem. Not quite at that point yet, however! https://github.com/gchp/iota

/shameless plug

This is an example of someone really mis-using the power of the microphone. I think antirez summed up quite well:

Technical leadership is a reward for the work you are capable to do, is not asked at conferences

If this was something Matt Stancliff really wanted, trying to stage a revolution of sorts from the stage is not the way to go about it. Prove yourself and rewards will come your way.

Perhaps due to the context of this link, I read "Apple" as "Apollo"

My background is primarily web development, however I've been writing a text editor in rust for a few months now. Prior to that, I had never written any software outside of the web.

Honestly, its not such a big change once you get into it. I'd encourage you to just give it a go, build something just for fun with it. Be it a command line tool, game, whatever. My experience has shown me that just because you've only been involved in web development, by no means limits you from systems/low level development!

Right, here goes...

- ability to handle large files without freezing or without a noticible drop in performance

- make all aspects of the editor scriptable. Emacs does this well, but I really don't like elisp. It will also be possible to script it in a number of languages, not limited to a single one.

- fast, like really fast. My Emacs config takes ten seconds to load, using IDEs takes much more than that to open. I want to make use of modern processor capabilities and minimise load time. Also to parallelise as much of the editing functionality as possible, so the user is never blocked by a task or operation.

- cross platform, easily installable. Some editors do this well, others don't. With iota you'll be able yo just download a binary and run it. No installation process, no dependencies. Same process to install on all machines.

I guess those are the main ones. Am on mobile right now so its hard to give more detail at the moment. I'll try update the motivations part of the readme with information like this today.

Another part of it which I didn't mention is that I've always wanted to build a text editor, they've always intrigued me. So this was me scratching the itch if you like. I also used it as an opportunity to learn rust, which I really like, incidentally.

To answer your question, I actually hadn't found one that suited me, fully. There are many that I like, but non which did it for me. It sounds a bit weird, but it needs to feel right, which none of then did for me. So that's why I started it. It seems others are interested in it too which is cool!

I'm currently building a similar project in Rust called iota: https://github.com/gchp/iota

I don't intend it to be a vim clone, however I'm currently adding some features which I've borrowed from vim. The main one being modal editing. Its much earlier on than this project, though.

As a side note, building a text editor is great fun, one of the most interesting projects I've worked on!

Because it's fun.

I love going from a blank slate to a working piece of software. I love that I can create things with just a terminal and a text editor.

The fact that I get paid to do it for a living is amazing, and something I find a little surreal from time-to-time.

I second this 100%! Jump in, you won't regret it! The rust guide is a great place to start: http://doc.rust-lang.org/guide.html

The folks on the IRC channel are supper helpful too. Don't be afraid to ask!