cmyr

T̙̙̳̠͕h̩͍̣̗͇̙e̖̙͇̺͍̝̙r̭̦̭̗̯͓͍̘e̮̜̼̝'̬͕̦̭̠s͖͎ ̙͎̫̭ͅa̲͖͙̟̹͚̱̜l̮͇w̥̙͙͎͍̻a͇̦̤̭̫̼͍͔y͖̰̱̣͉̗̼̟̘s̲͇̼̻̻͍͉ ̠̞̦̲̝̱̗o̪n͈͎̞e̥͈̠̬͍̬̱̲ ̪̼̝̞̮g̥ṵ͈̥y͎̤͖̥ ̜̬ṯ̳̗̜̼̱̬r̠̫̪̺̫y̗͍͔̜͇͍ị̼̲n̖̥͙͓̹̘̞̳͕g͕̗ͅ ̪t̤o̰̞̱͓̫̙̙͔͕ ͍r̟u̺͈̞͚͖i͖͈̗̭͖̯n͈̼̜̹ ͙̙̪̰̫̼͓i̻̩̰̪t̤̦̖͉ ͇̳̰f͔̥͕̟̝o͉̬r̥͕̝̬̰ ̟̪͇̺͉̰̭ḛ̙͕͕̜v͚ͅe̥͈̰̮̭̼ṟ̥͔͎̯̖y̤̞̮̳̪̞̰o͖̱͙͖̜̦n̙̦e̘̰͉͓̫̥̞ ̩e͖͕ḽ̭̪͚͕ͅs̮̺̣̬͍ḙ̬̫̹̻̤͖̗.͎

Indeed, ever since I realized I could get medical care without paying for it I've been going out and getting cancer a couple times a week.

What is "risk production"? I can't help but reading it as something like, "we even risk producing some chips at some point!", which I presume isn't quite it.

This was exactly the case that got me into Rust; I had something that needed to be fast and needed to be callable from a variety of languages & environments (from python, C and Java immediately, and expecting to add swift later) but it also had to do a lot of unicode string handling, and I just _really_ didn't want to do it in C. After making sure that everything I needed was possible, I did it in Rust and it was an absolute pleasure; I haven't looked back.

Another great post on this topic, by the other of ripgrep: https://blog.burntsushi.net/transducers/

Very cool. A friend put me on to TIS-100 when I was curious to play around with assembly, and it was a very helpful (and fun) introduction.

Square furniture, I presume?

Wasn't Vice City was the Grand Theft Auto of 2002/03? ;)

More to the original point, the first GTA remains along with Age of Empires one of my all-time favourite games. It's easy to forget in light of the franchise it became what a novel and crazy little game that was.

From reading these threads previously, the answer is generally 'marketing'.

Nothing in these results should really surprise anyone. Go is a good tool for writing networking services, but it is not (and does not intend to be) a systems language.

For another perspective, look at Go versus Python: https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

They aren't more burdened, but they are the last line of defence.

If I'm billing hourly and I'm billing an 8 hour day, I'm including a 30 minute lunch, regardless of rate. Anything longer than that is off the clock. If I'm billing 4 hours, then sure, no lunch. This is only true if I have a single client project on the go; if I'm billing piecemeal through the day (which I never want to do) then yes I'm eating on my own time.

I get being hesitant to bill for certain kinds of troubleshooting, but I think it comes down a lot to what the scope of the project is. If I'm on something that is multiple weeks of work, and I'm dealing with a problem that I would be encountering and would be expected to solve if I were working full-time, then it's billable.

You aren't billing for _debugging_?

I would also include in my billing a 30 minute lunch over an 8 hour day, which is the minimum mandated by local (Canadian) labour law, and I would bill for any incoming calls and email that is related to the project I'm working on.

I'm definitely aware of how different my time feels when I'm billing, and I've tried to relax a bit. I think billing daily or weekly is always better than hourly.

Fitzpatrick? (https://en.wikipedia.org/wiki/Fitzpatrick_scale)

As currently architected, the frontend is responsible for sending the core events such as "copy", "delete to start of line", or "insert 'a'". On xi-mac, the default experience is intended to closely match the behaviour of other native Cocoa apps, and to generally respect platform idioms.

Please!

Is this a debug build or a release build? File loading isn't particularly fast atm (we load the whole file into memory) but once a file is open I can breeze through it..

There's no technical reason you shouldn't be able to happily scroll through (and edit) a 15MB json file; and search for an arbitrary string should take ~10ms (ballpark from playing around with ripgrep just now), certainly not slow enough to merit big up front indexing costs.

Okay fair point, my emacs experience is limited to installing spacemacs once while procrastinating.

Maybe we're using different definitions of "native". In the most common case, both of these editors use the cross-platform "VT-100 UI Toolkit" (e.g. ansi escape codes in your terminal emulator), regardless of platform. Some exceptions do exist. But native as it's being used in relation to this project refers specifically to whatever frontend framework is 'the standard' for a given platform, where one exists.

Xi's medium-range plans for modal editing support[1] are intended to be modular/general enough that you could plug in whatever particular modal-editing implementation you'd like.

1: https://github.com/google/xi-editor/issues/302

The official frontend is a Cocoa/Swift app: https://github.com/google/xi-mac

Adding another perspective: as someone who follows kernel news very casually, it's pretty near impossible for me to determine which instances of "Linus curses something/someone out" are related to actual Serious Things Deserving My Attention. There's a bit of boy-who-cried-wolf to the whole thing.

US also has the New Yorker, the Atlantic, Harpers, and a few other very good monthlies.

As someone who comes to software engineering from a non-traditional background, I've found Crafting Interpreters particularly useful for helping to fill in a bunch of stuff that I missed out on by never doing a Compilers class. Thank you!

While you certainly may use it for free, you also have the option of donating! https://www.iterm2.com/donate.html

We can only speculate about what happened here. Whatever it was, it happened in some mixed cloud of panic, fear, anger, shame, &c &c. I think the whole project of trying to evaluate the rationality of Madsen's response is poorly formed.

Something terrible happened on the sub. We don't know what, yet. Maybe we will some day. In the interim, I think there's room for compassion towards all involved.

From a brief bit of clicking around, the author has: designed several typefaces[1], written a long text on typography[cited previously], and has done enough programming to have developed the publishing framework he uses in his books[2], and to have written another book on a programming topic[3].

While I don't agree with much of this blog post, I certainly think the author has put in enough work to have their work taken seriously in this particular domain, and generally seems like a pretty interesting person.

1. http://practicaltypography.com/equity.html

2. http://docs.racket-lang.org/pollen/

3. http://beautifulracket.com

Or it could be that the best resources for information about a specific language exist outside of stackoverflow; I think this is often the case with Rust, for instance, where I will generally turn to users.rust-lang.org, or IRC for questions that I would turn to SO for in other languages; and when I end up googling particular questions I more often end up at somebody's personal blog.

By various estimates the replacement cost of the US grid is about 2-5 _trillion_ (taxpayer's) dollars[1].

1. http://www.businessinsider.com/replacing-us-electrical-grid-...