122 karma · joined August 29, 2013
Kind of uninteresting for most players, but hey; this IS hacker news.
Basically everything I used on Win7 works / can be installed just the same on Win10. .msi packages, Chocolatey packages, oddball Win32 apps I've found over the years, even portable programs that haven't been updated since XP. Only had one program mysteriously uninstalled itself when I made the move: IronRuby. I'm not sure if Windows Store apps can be sideloaded, but the only ones I have installed came installed by default. Easy to avoid.
(I'm largely expanding on what Santosh83 said in a sibling post.)
Eddyit: Spelshing.
Probably helps too that I have beige walls and a small desk lamp beside me. Using the desk lamp instead of the full room light / a completely black room helps limit eyestrain.
I guess you could say that is even less reliance on GC than C++ has, with smart pointers being part of the standard.
[1] http://keepass.info/help/base/security.html#secdesktop This said, both secure desktops and auto-type obfuscation are turned off by default...
I'm curious about this, although I don't think this is the first time I've heard D described as having a script-y feel to it. It sounds along the same lines as people describing Go as almost a scripting language, or comparing it to them. Neither Go nor D seem especially dynamic, both have compilers for reference implementations, both look more like C than Python. (To my eyes at least; I've never tried either one. Thus this question.)
Is it primarily the speed of the compilers? Both DMD and g6/g7/g8 boast very fast compiles, and Go uses somewhat script-y tools... but #!/usr/local/bin/tcc -run hasn't changed C's reputation. Fast compiling and memory safety, maybe?
That isn't from a 'position of power'. That's avoiding transactions where the other party has a position of power. Two countries wishing to operate from a position of power may engage in a cold war or the like.
Not to say a social safety net to ensure life never hangs in the balance wouldn't prevent some unfair transactions from occurring...
But to avoid the costs of the Ares V, we wanted to do the entire thing using nothing but existing off-the-shelf available LVs to do the entire thing. If we'd gone the route of even a small custom LV, we would have the constant overhead of maintaining multiple launch pads that sat idle for 2 years at a time, just to launch something each launch window to Mars. Instead, our plan began with the Delta IV-H lobbing payloads trans-Mars. It has a payload of just over ~9T doing that. It could also fly three or four payloads per launch window, Vandenburg and the Cape, both at the start and the end of the window for a two week turnaround on each launch pad. Of course, suboptimal timing and suboptimal inclinations will cut into that 9T slightly. Further, we could make use of things like the Mitsubishi H-IIA [2], Atlas V 551 or Heavy (would need modest new development, or the 551 which is a bit weaker), Ariane V and maybe Proton (tho Proton is quite weak on high energy flights). Falcon 9 Heavy could eventually be added to that list (I think we were already talking about F9H in 2007...). That gets you maybe 6-9 payloads per launch window to Mars, of 6-9 tons depending on the launcher. That was our working budget for each payload.
We managed to account for just about everything to do with the surface base using nothing but those small payloads... Planned out a standard design for a small descent vehicle in I think 1500kg to 2500kg which could land most of the rest of the mass as payload. We could do Earthworks (or Marsworks... dirtmoving / digging) using using some small remote-controlled construction equipment of 2-3T each. [3] Food, water and other supplies could pretty easily fit in smallish pieces like that. Used solar panels in place of Mars Direct's nuke for political feasibility / scalability to small payload deliveries. Also talked a bit about assembling a shelter using either the landed capsules for rooms, or assembling rooms from parts (I don't remember which). A part I was a bit uneasy about that some others thought was trivial enough, was building a new launch vehicle from parts on the surface... We'd be using small modular segments to build stages, scaffolding to assemble everything together and connect the stages, and all of this would be done outdoors. I was kinda worried about getting sand between the staging components or in the engines.
The part we didn't manage to fit into the initial constraints of 9 ton payloads, all direct-to-Mars, was the actual crew transport there (we were fine-ish for the return). We stretched kinda far, pulled compromises nobody would really take, and got a 1-crew capsule to weigh in at 11T-12T. And that's with basically no redundancy! The entire thing would be a small can with a solar wing for power, life support for 6 months, and no way for the pilot to survive a launch failure from Earth. The capsule would fly straight to Mars, pilot would don a suit, depressurize the capsule and get in a MOOSE-alike [4] module and travel to the Martian surface in that. They would also be dependent on the entry trajectory for their life, as they'd have to walk to base on landing.
From there our plans started to look a bit more "traditional" with either an HLV snuck in there just for the crew (and not the base) or orbital assembly of an orbital ship. Say, something with plenty of life support of its own, just does Earth-Mars-Earth and gets the crew to and from the base. The ship itself would be a rather substantial project to build, but at least it could ignore landing much payload. And the ascent vehicle from Mars would only need to worry about orbit, not escape velocity.
[1]https://web.archive.org/web/20070810053610/http://uplink.spa... Ok, so the thread Mars 9 Tons at a Time wasn't archived at all. But there it was, August 2007.
[2]https://en.wikipedia.org/wiki/H-IIA
[3] http://www.cat.com/en_US/products/new/equipment/excavators/m... For example, is a smallish piece of equipment which can take many different parts on the end of the arm, work very slowly as a bulldozer, and fit inside our payload budget. We'd need something mechanically different, but probably that size / style of machine, to work remotely in very low temperatures. Shortly after our that thread, one of the construction equipment companies produced concept art describing something like that on The Moon with actuators (I think) in place of the hydraulics. Some folks complained that they were just advertising their stuff on The Moon to look cool.
[4] http://www.astronautix.com/craft/moose.htm Not terribly confidence-inspiring.
I'm not sure how well maintained those backends are, and I've read TCC isn't really stable enough to use in production, between the incomplete x64 backend and just general bugs... Solving those may yet push TCC a fair bit beyond 60k LOC.
Say, PL's are materials. They are something that useful things "tools" are fashioned out of. The properties of a material affect the entire thing built out of it, in modest but pervasive ways. Some programs are built in more than one language, this could be seen as an object built with different materials for different parts. Now, whether mainstream languages are analogous to different iron alloys, wood, concrete or plastic is a different discussion. (And maybe another exercise in taking an analogy too far...)
Not sure where I saw this analogy first, since I can't find it on LtU...
Aren't these somewhat different details to know tho, compared to knowing the insides of git? Knowing the commands, and options available in an editor is familiarity with an interface. You don't need to know exactly how it stores the buffer so it can stay responsive with large files, you don't need to know the rendering algorithms involved, etc. etc. Just the same, I don't think being able to use a compiler effectively depends on knowing how it does register allocation, or knowing if the parser is LALR or recursive descent.
These are all implementation details. Good interfaces generally abstract over them, and present the user with what they need to use it. Version control being necessary doesn't change how people should approach learning it. At least, no more than we should expect good drivers to understand piston engines. (Though, drivers of manual transmission cars should probably understand clutches. Maybe Git is comparable to that?)
[0] http://stackoverflow.com/questions/2752979/using-jruby-jytho...
[0] One former dev on one of the Iron* languages posted on reddit about how the CLR failed on its cross language ambitions. I can't find the post, but they gradually found it was mostly C# centric anyways, and ports of other languages were mostly incompatible and second-class
[1] http://whiteknight.github.io/2015/01/15/parrottheend.html
[2] http://ironpython.net/announcements/ for what it's worth...
Edit: PL's aren't physics.
Can Rust still do phantom types, and I just can't see them anywhere in the language reference?
Ariane 5 went expendable specifically to make it feasible to build, where Sanger and similar SSTO re-usable spaceplanes were too far-fetched to build.