Hacker Newsnew | past | comments | ask | show | jobs | submit | more mcmire's commentslogin

This (and actually bodily augmentation in general) seems like something that 3D printing is perfectly suited for. I see this sort of thing blowing up in the next 10 years.


Not true. Regexes have been around for a long time and there are a few standards -- POSIX basic, POSIX extended, and PCRE. Any language/tool worth its salt these days will follow one of these three implementations (usually it's PCRE as it's the most complete). It's usually older tools like awk, vim, find, etc. that have their own quirks -- they were created before these standards existed and so they generally follow extended regex but then introduce their own syntax for certain concepts (in vim, for instance, \<...\> does the same thing as \b...\b in PCRE).


Didn't you just make the previous commenters point, that regex implementations vary? Within those three there are variations too with the flags and how they implement word boundaries (either exclusion of word characters or inclusion of certain spacing chars)


I think the case that there are too many implementations is overstated. Almost everyone can get away with knowing only PCRE these days. Most programmers I've know don't even know that they're using PCRE, they just know they're using "regexes"


I haven't had the incentive to learn regexes well enough to understand why I have to escape random things in different languages and environments. And occasionally something will fail to work all my cases and I have to fall back on a non-regex way of matching.

I've generally found that my practice is basically "try regex; if it doesn't work after ten minutes of effort, abandon regex completely".


Wow this is so great. As a musician listening to a classical piece (well and an engineer too) I often think, "How does this work? I hear a clarinet here, is that what it is or something else?" So yeah, very cool.


Thanks! :)


Yes, you should master JavaScript -- it's used all over the web and people will continue using it that way. But I disagree it's making all other languages irrelevant and that it's a "game changer". Devices are not going to be coded in JS any time soon (the runtime isn't robust enough and the language is not designed to be used that way). Yes, people may use asm.js more and more to convert bigger programs to run on the web, which is super cool, but asm.js isn't JavaScript.

So master JavaScript, but then learn Rust, Elixir, Go, Haskell, and Lisp, too. These are as much "game changers" as anything else.


"Devices are not going to be coded in JS any time soon"

http://technical.io/


Oh, there is http://pijs.io as well.


Thanks for the clarification. So weird. Was this just a random thing? Does anyone know?


No cause of death has been given.

The common speculation floating around is a heart attack, but there isn't any solid evidence I know of for this.


No one has come out in regards to the cause of death. Tragic loss :(


Yeah, I'm bummed to hear this news too, I've been rooting for them since the beginning. Granted Google Maps is way better than Waze, but, I think the whole crowdsourcing angle that Waze takes is interesting, and I think it's impressive how far they've gotten with a small team comparatively.


Isn't this the theme update they've been working on for over a year? I seem to have heard word about this a long time ago.


Right, at first I thought this was done by the creators of voxel.js. Perhaps this was an exercise for the OP and that is fine but it seems there is a fair bit of reinventing the wheel going on here.


Look, here's the reality. You say they could keep you on for another year and yet they obviously see you as an employee who will do whatever they tell you to do. While this is far too common, it obviously means they don't care about your opinions or whether you are happy there.

At the same time you have to look at it from their perspective. You don't want to suddenly leave. I think two weeks is too short for this sort of situation. I worked with a guy who gave four months' notice; that's the agreement he made with my boss, and when those four months were over he left peaceably. Granted, we did have other developers to take over, but we also happened to hire more people in the meantime too.

Just be honest and tell management what you are feeling. You need to push them to hire another developer as good as you are ASAP (vet them personally). If they are not willing to do this, then they do not care about their product -- but that is their problem and not yours. But if they are willing, when the new person comes in, teach them what you've built. This is going to take time. I don't think one or even two months is enough time, you might consider more like four months. You can start now by writing up all the stuff you know.

If you are concerned about not burning any bridges (and believe me I would be too) then this is a surefire way of doing that. You just have to make sure they agree you will no longer be working with them after the allotted amount of time... and then stick to it.


"I’m Marco Arment: creator of Instapaper..."


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: