JDevlieghere

Apple | Software Engineer - Developer Tools/LLDB | London, UK | ONSITE (3 days/week in office)

The LLDB team is hiring an engineer to work on the debugger, which is used internally across Apple and externally by millions of developers. You'll drive features and improvements in LLDB, collaborating across teams working on the OS and toolchain. Responsibilities range from supporting new hardware and platforms to developing debugging features, with most work open-source (llvm.org & swift.org).

If you're passionate about developer tools with experience in system-level programming and knowledge of compiler/debugger/OS internals, we'd love to hear from you!

https://jobs.apple.com/en-gb/details/200643284/debugger-engi...

Apple | Debugger Engineer | Full-time | Onsite | Cupertino

The LLDB team at Apple is looking for an engineer to work on the LLDB debugger. LLDB is a core part of Apple's developer tools, used internally to debug Apple's software stack and externally by millions of developers. You’ll be able to work on different levels of the stack: from supporting our existing and upcoming platforms to developing new features to make debugging even better. Most of your work will be open source, on llvm.org (http://llvm.org/) and github.com (http://github.com/) where you’ll collaborate with the LLVM and Swift community.

If you love working on low-level tools you should check out the details here: https://jobs.apple.com/en-us/details/200311412/debugger-engi...

Indeed, the commit hash reported in the version corresponds to something that landed on master at 11PM this Monday.

The one for Chris Lattner is definitely off: https://twitter.com/clattner_llvm/status/1150992062365310977

I wish more developers wrote code with a mute keyboard.

LLVM adopted a new version scheme which made the minor version redundant. IIRC someone suggested to remove it and nobody objected.

http://blog.llvm.org/2016/12/llvms-new-versioning-scheme.htm...

> What for you might need it on iOS? Server is meant to run on a development machine.

While I totally agree, I can see the author's point. Think for example about Swift Playgrounds.

Yes, exactly this. If you have 3 different editors and 3 different languages, you potentially end up with 9 different implementation. LSP means that the same can be achieved by one implementation per language and one plugin per editor.

In addition to what everyone else has said, something I'd find really useful would be going in the other direction. Just mark some keys and it tells you what chord you're playing.

> Let’s face it, programming books suck.

While I agree that there are a lot of bad books out there, I don't agree that programming books suck in general. I very much prefer a well structured book over one of those chaotic tutorials that leave me with more questions than answers. Especially for languages where the "why" matters a lot more than the "how".

> It’s a lot like the way you may have already been doing it, just with more learning.

Maybe that's the reason why I disagree. Indeed, they way I read a book is by putting its content into practice.

Why would you need to recompile the compiler? Both variants only provide read access.

From the home and about page it seems like this was developed in the context of teaching a course at the Imperial College London. I wouldn't be surprised if there was just so much bureaucracy involved in getting this open source that the author deemed it not really worth it.

This is how I understood it as well.

This is why I check the comments first, thanks!

Too bad IPv6 is again ignored completely; not even a mention in the article.

Indeed, it's portable and part of the standard. Personally I'm a big fan of this implementation: https://github.com/progschj/ThreadPool/

GuardSquare | Software Engineer C++ / LLVM | Leuven, Belgium | Full-Time | On-Site

GuardSquare is looking for a software engineer with an interest in software security. You have knowledge of compiler technologies (LLVM) or the Mach and/or Linux kernel and you are definitely not afraid of disassemblers or debuggers.

For more information have a look at our website, where you can apply online: https://www.guardsquare.com/en/jobs

Same here in Belgium :-(

GuardSquare | Software Engineer C++ / LLVM | Leuven, Belgium | Full-Time | On-Site

GuardSquare is looking for a software engineer with an interest in software security. You have knowledge of compiler technologies (LLVM) or the Mach and/or Linux kernel and you are definitely not afraid of disassemblers and debuggers. Our team is building iXGuard, software that protects iOS applications through obfuscation and encryption. Think ProGuard (our open source solution for Java) but for Objective-C and Swift.

For more information have a look on our website: https://www.guardsquare.com/en/jobs

GuardSquare | Software Engineer C++ / LLVM | Leuven, Belgium | Full-Time | On-Site

GuardSquare is looking for a software engineer with an interest in software security. You have knowledge of compiler technologies (LLVM) or the Mach and/or Linux kernel and you are definitely not afraid of disassemblers and debuggers. Our team is building iXGuard, software that protects iOS applications through obfuscation and encryption. Think ProGuard (our open source solution for Java) but for Objective-C and Swift.

For more information have a look on our website: https://www.guardsquare.com/en/jobs

You can apply online or e-mail me directly at [email protected].

After six year, I recently built myself a new desktop computer. My budget was a little higher, but I think it's worth sharing.

Hardware: Asrock EP2C602-4L-D16, 2x Intel Xeon E5-2670, 8x 8GB Hynix PC3-10600R DDR3 ECC, 2x Noctua NH-U12DX i4, Corsair RM850i, Phanteks Enthoo Pro

Because I bought the CPUs and the RAM second hand, they only cost me 390 euros. Even when buying all the other stuff brand new, the total was still less than a 1000 euros. To be fair that's without an SSD and Graphics card, because I kept those from my previous set-up. With 32 logical cores it's perfect for compiling, which is what I use it for. If you're interested, you might want to have a look at this techspot article and see how a similar build compares to recent i7's: http://www.techspot.com/review/1155-affordable-dual-xeon-pc/