HNHacker News
TopNewBestAskShowJobs

Solarsail

122 karma · joined August 29, 2013

Yet another space nut. Go by Solarspot on some other sites. http://solarspot.netlify.com/
submissionscomments
Solarsail··on How Technology Hijacks People’s Minds
That's not first and foremost CO2, though. Many other forms of pollution tend to be far worse to local environment. Addressing those might involve things like catalytic converters on ships and the like.
Solarsail··on Dwarf Fortress' creator on how he's 42% towards simulating existence
Not really contradicting you here, but DFHack for the last couple of years has worked as a shim between DF and the SDL library. Substantially simplified the process of changing the game's behaviour, and mostly eliminated the need to poke around memory addresses. DFHack is also essentially the third party modding library for everyone else, with only Dwarf Therapist still poking around memory last I heard.

Kind of uninteresting for most players, but hey; this IS hacker news.

Solarsail··on ESP8266: A $5 microcontroller with wi-fi that runs Python
Very tangentially related, but: if FRAM on the MSP430 saves its state on power loss, my mind went straight to Smalltalk. It's like hardware support for saving an image. Tho from an efficiency standpoint, smalltalk might be pushing it more than MicroPython is. That, and a smalltalk editor on a machine too small to fit a vi clone might be even more of a stretch. lol.
Solarsail··on Introduction to the Zig Programming Language
I wonder how feasible it would be to decouple data size from type & overflow semantics, a la this comment:

https://news.ycombinator.com/item?id=7103347

Solarsail··on Why you should not develop apps for Windows 10
(Slightly anecdotal answer, but...)

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.)

Solarsail··on A critique of "How to C in 2016"
Wouldn't debugging / testability imply this is a fairly large proportion of programs? Having a calculation give different results on different hardware would make testing difficult: http://yosefk.com/blog/consistency-how-to-defeat-the-purpose...
Solarsail··on Android NDK: GCC is now deprecated, everyone should be switching to Clang
Those are all general issues that would apply to developing GCC, aside from compile times and tooling integration they don't effect NDK users. So the question goes back to being specific, why deprecate GCC while it's still popular elsewhere and well supported on this hardware?

Eddyit: Spelshing.

Solarsail··on How I became a morning person
So, my sleep cycle was about like what yours sounds like, I'd often slip back half an hour from one day to the next... But rarely if ever had a sleep cycle under 24 hours. Tried out f.lux a month back, and... Well I'm still on a strange sleep cycle, but a different one. lol. Slept from 8pm yesterday to 3am today, snoozed until 4am. Often I've slept a bit less than normal, but starting far earlier, and waking up early. Maybe that's just a result of only using it for a month, so far.

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.

Solarsail··on Ways to Avoid Complexity in Modern C++ [pdf]
Doesn't have one. Reference counting is available as a (what looks like third-party) library: http://www.adacore.com/adaanswers/gems/gem-97-reference-coun...

I guess you could say that is even less reliance on GC than C++ has, with smart pointers being part of the standard.

Solarsail··on Even the LastPass Will Be Stolen
Well, WRT to malware, KeePass can somewhat mitigate generalized threats. Say, in-memory encryption to protect against memory dumps, using a secure desktop [1] for the master password, and typing obfuscation during auto-type to protect against keyloggers. Well, keyloggers that aren't written with KeePass in mind, at least. Both of those would give it a modest edge over plain text in an encrypted container.

[1] http://keepass.info/help/base/security.html#secdesktop This said, both secure desktops and auto-type obfuscation are turned off by default...

Solarsail··on D 2.069.0 released, compiler automatically ported from C++ to D
> D has more of a scripting language feel to me.

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?

Solarsail··on 'Extreme poverty' to fall below 10% of world population for first time
Picking a nit, but:

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...

Solarsail··on A Minimal Architecture for Human Journeys to Mars
Well, the avoidance of docking was primarily because this was a thought experiment, not quite optimizing for a global optima. We wanted to see if a Mars mission could be mounted within those tight constraints, and set about with those constraints as unwavering. Why avoiding docking was one of them, was a requirement from Mars Direct. (Flipping through A Case For Mars for a minute wasn't enough to find the reasoning...) If you wanted to do a mission with minimal assembly but with docking... I'm not sure you could get a ship with a dry mass of <25T to launch to LEO. Say, with a sizeable upper stage for orbit insertion, habitat module and life support storage space (even with the food / water / fuel all brought up later). Even a fairly large Bigelow module, electrical equipment and pressurized space for food is going to be more than a Delta IV-H can take to LEO... And then an empty upper stage big enough needs a lot of volume. Maybe two flights for assembly, and then launch supplies up?
Solarsail··on A Minimal Architecture for Human Journeys to Mars
A possibly irrelevant nostalgic detour, but I'm reminded of a thought experiment I contributed to once [1].. Called Mars 9 Tons at a Time. Basically use Zubrin's Mars Direct as the baseline plan, but do it without the Ares 5 he described or another HLV. Which has the effect that we would launch everything direct to Mars, no rendezvous or docking prior to the Martian surface. Primarily on the hypothesis that docking the parts together would add the cost of an assembly facility, and complicating the components enough to be dock-able together or heavily suboptimal to support simple assembly.

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.

Solarsail··on How to compile C apps with musl and Clang
As a (mostly ignorable) sidenote, TCC does support a couple of non-intel ISAs. At least 4-5k LOC beween arm-gen.c and C67-gen.c, compiled from an IR https://github.com/LuaDist/tcc/blob/master/il-opcodes.h If this repository's anything to go by: https://github.com/LuaDist/tcc

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.

Solarsail··on The Intel Xeon E7-8800 v3 Review: The POWER8 Killer?
Along with the other answers here, things like distributed processing projects tend to be embarrassingly parallel. I was running distributed.net OGR for a while, and that runs quite a bit better on many modest cores. Almost all my other programs bottleneck on disk / RAM speed, or RAM size... The OGR project in particular is also far more efficient on CPUs than on GPUs, since it is an entirely integer workload.
Solarsail··on Death to C
Even in C's own domain it still faces issues with undefined behavior. AFIAK, this is a problem Rust still doesn't face even while issuing ASM commands.
Solarsail··on Can Your Static Type System Handle Linear Algebra? (2014)
PL's as tools is a half-accurate analogy. If you're going to stretch it that far, shouldn't you use something more accurate? Or better, not use an analogy for something that detailed?

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...

Solarsail··on MLRISC – A framework for retargetable and optimizing compiler back ends
Is this still maintained? It seems SML/NJ still uses it, do they track any sort of development of it? Are they the main supporters of the project? The website seems to date to 2003, and refers to architectures like Itanium as upcoming. It also doesn't mention x64 at all.
Solarsail··on Inform: A Language for Interactive Fiction
Wouldn't that have been with a different language? Inform 7 is a vastly different language from Inform 1-6 (which were relatively Algol-like), and only came out in 2006.
Solarsail··on Git from the inside out
>I know my text editor very well so that I can write efficiently. I know my compiler well enough to use it to build my programs in the various configurations I need.

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?)

Solarsail··on The ups of downs of porting 50k lines of C++ to Go
In addition to those, there is Iota. Which is completely special-cased syntax sugar, which is not reusable outside of a single context. You can't use it at all more generally, and get potentially non-obvious code from using plain integers silently.
Solarsail··on ‘Anti-petroleum’ movement a growing security threat to Canada, RCMP say
As noted by https://news.ycombinator.com/item?id=9063463 tabling a bill is not getting rid of it; Tabling a bill is the first step to passing it.
Solarsail··on Introduction to the Common Language Runtime (2007)
Interesting! Does that (partially) obsolete this answer [0]? Do Ruby programs see Java objects as a separate kind of Object, or is it seamless? Is there a translation layer anywhere? Does JRuby-Rack have to use wrappers for Java functions?

[0] http://stackoverflow.com/questions/2752979/using-jruby-jytho...

Solarsail··on Introduction to the Common Language Runtime (2007)
Isn't this a general problem of cross-language VMs? Different languages need different object models, and different data representations. [0] At least according to one Parrot developer, the Parrot object model was one of the biggest pain points for porting JS/Ruby/Python to Parrot... Where that object model was meant to be universal, and work for any language. [1] That said, IronPython does still semi-exist [2], and I'm not sure how well JRuby handles interoperability with Java or Jython...

[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...

Solarsail··on PyPy 2.5.0 released
They would have their work cut out for them, that I can see. They could reuse the .moarvm bytecode and file format, the NQP compiler and Moar backend [0]. I think many of the test cases are even common between the three backends... So all that's left to re-implement is a bytecode interpreter, IO facilities and FFI. That is, if my understanding of MoarVM is accurate.

[0] (https://github.com/perl6/nqp/tree/master/src/vm)

Solarsail··on What Blocks Ruby and Python from Getting to JavaScript V8 Speed?
Isn't finding what function to call at a particular function call much easier in Lisp (or Julia) than it is in Python/Ruby/JS? The vast numbers of CL and Scheme compilers are relatively easy to write, exactly because the languages leave (somewhat) less to decide / change at runtime than Python/Ruby/JS.

Edit: PL's aren't physics.

Solarsail··on Announcing Rust 1.0 Alpha
Haven't used Rust, but I wonder what you could use in place of the phantom types? Are Traits capable of filling this role? Am I completely misreading what Traits are?

Can Rust still do phantom types, and I just can't see them anywhere in the language reference?

Solarsail··on The Future of Space Launch Is Near
The shuttle used them as early-flight boosters. Same trick used by Ariane V, Titan III / IV, Delta II / III / IV, endless other big vehicles... They are much cheaper to develop per thrust than liquids (They are expensive per size, but scale up to higher thrusts well), and you often want most of your thrust early on rather than later. Solid boosters you ditch after 30s or a minute raise your T/W ratio so you don't loose as much fuel to gravity losses, and get your more efficient but less powerful liquids into the upper atmosphere. Both Ariane V and Shuttle typify this, with almost all liftoff thrust from the solids, and a small, expensive hydrogen-burning engine continuing to most of orbital velocity. For the shuttle, this was aimed at reusablility, they could do most of their work on expensive engines, and not need to pay that cost every flight. Ariane did it so it could make near-orbit with only engines it lit on the pad, for reliability sake. (Planned for the Hercules spaceplane, which wouldn't have used the upper stages that satellites would eventually use.)
Solarsail··on The Future of Space Launch Is Near
"Dino-space" is a term I hadn't heard before... Is this a newer version of the "Old-space" that people were talking about in 2005? As for re-usability on the existing designs, there were many impressive concepts for that floating around in the 80's, before they were all killed off for the Shuttle. But more recently it's not like they're just protecting what they've always had, fending off the little guy. The EELV program was rather innovative, and rather successfully reduced costs and probably improved launch reliability using some fairly unusual approaches to vehicle design. They worked out sub-optimally, because commercial demand was weaker than predicted (and never materialized for Delta IV), and Boeing wasn't exactly about to sell at a loss to boost sales. I've heard a few people argue, since the ULA merger, that ULA as a company doesn't really have the money to try to re-do the EELV's anymore, only somewhat breaking-even while SpaceX gets actual investments. Tho that might be disgruntled greybeards complaining...

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.

← PreviousPage 2 of 4Next →