imode

I'd like to see some hardware that implements records in, well, hardware. collections of fields with counts and sizes. it'd be nice to do away with the idea that we're haphazardly (and implicitly) overlaying things like structs onto an untyped one-dimensional array of bytes (or in some cases, machine words).

that to me is more important than straight bounds checking for arrays, because it implies something a little stronger.

repeat after me:

"I will not share something I do not want others to mirror."

if you don't want us to gain a copy of it, don't host it. simple rule. if you don't like it, choose another content platform.

this is so awesome!

you could turn this into a MUD by just letting people in via SSH. if you supported auto-reloading your YAML files during play (or just keeping track of loaded files), you could support online creation!

I'm fascinated.

what is it like to 'bootstrap' D? I know in many languages you can forego the standard library and 'bootstrap' yourself on small platforms (C being the main example).

point voxels! :D

I've always wanted to try point voxels out. Ace of Spades uses them for models.

awesome work!

if you squint, it all looks like state machines!

not caring about performance destroys faith in projects. if the things we write can't be as performant as we like, we'll use a different language and your project will fade.

pretty simple concept. surprised that people don't understand that.

(mind you, python is about as performant as I like for the tasks I use it for, so ymmv with the above.)

his comment is effectively constructive criticism. stop marking him out to be such a terrible person for criticizing something that someone has authored. no work is immune to that, and creators don't deserve our "positive energy" if their creations, in our eyes, leave something to be desired. you don't get praise just because you created something, nor do you deserve it.

please don't defend thin-skinned creators, and also please don't speak for them when you don't know or understand their intensions.

on the upside, I can now watch Netflix on Linux using Firefox, and I can opt in or opt out of the DRM facilities...

on the downside, as everybody else has pointed out, we now have DRM encroaching onto an open standard.

I guess I'll take it as I go.

I don't think anybody is going to pirate your wedding planner software. you being smug about something you have no control over (re: piracy) is also not going to do anything either.

been there. crashed a client's website on a friday by updating the wrong plugins for a Joomla site.

given a sufficiently complex dependency chain for presented problems, anybody can be a 'team-member-1'.

mistakes happen at all levels.

incredible.

to think it was just yesterday that Metroid Prime 2: Echoes failed to run properly on the thing (along with Metroid Prime).

this project has come so far since 2008.

A story like this. "videogames are sucking people in" has been replayed when WoW was popular. and even the article references prior stories.

slow news day, huh? seems this story is aired about every 2-3 years...

EDIT: I'm being downvoted for pointing out that these kinds of articles have been rehashed for years? thanks. continue on, then.

I wish I could. but I don't have the knowledge or the time.

thanks. this is pretty scary.

guess I'll be using Chromium when that day comes, as I'd rather not run PulseAudio.

on arch here. haven't seen the problem yet, and I'm on 52.0. why am I not affected? I don't have pulseaudio installed (only some client libraries. lib32-libpulse, to be precise).

this doesn't look good. thanks for the post.

yup!

I'm creating a small virtual machine based around the idea of associative memory (read: tuplespaces). I'm going to use it to write a ton of declarative code for smaller devices and for some of my own projects.

the opcodes are still in a state of flux, but a partial implementation exists in Python, with the intent of porting everything to C and getting a spec up. you have operations like 'match', 'exists', 'assert', 'retract', mathematical operations...

...oh, and no callstack. ;)

what you want to learn has been learned before a thousand times.

never fear walking on a well-worn path.

definitely. plenty of literature on this. the problem, however, is how the delays are calculated. FPGAs have a lot more intermediate logic to determine which gates are connected to what, and that means intermediate delays that you need to account for.

not saying it can't be done or even that it's hard. just a different process.

I don't really want to be seeing some person's genitals, mainly because we live in a culture based around hiding your junk (which I'm not opposed to). someone's words, however, are totally transient and I'm free to tune them out. I'm not exactly free to not look at somebody.

I can put headphones on. I can't put a blindfold on.

hats indoors? really? you think that's disrespectful?

there's a severe lack of common sense nowadays, and uppity folks are proof of it. fuck words. :P

shouldn't this be marked with "Ask HN:"?

no matter how intelligent or educated you may be, words are just words. if they harm your sensibilities, perhaps try ignoring people.

besides, a loud expletive is sometimes required in certain situations. :P

one of the main issues in asynchronous design is the idea of gate delays, i.e delays in individual logic gates that compound inside of a circuit.

there are ways of dealing with this. delay-insensitive circuitry, QDI circuitry, micropipelines...

if you're interested as to the "state of the art", as I learned it, look no further than Principles of Asynchronous Circuit Design[1], a fantastic book. a PDF[2] is also available. another fascinating piece of work are Micropipelines[3] by none other than Sutherland.

the main benefit for asynchronous architectures is their ability to be expressed in software. the primitives used (as you'll read) function very much like traditional software constructs based around control and dataflow. this is very easy when your entire architecture is based around pipelines, which can choose to hold and "re-transmit" data.

asynchronous design isn't dead or disadvantageous. we just forgot about it for some reason.

[1]: http://www.springer.com/us/book/9780792376132 [2]: http://www.orbit.dtu.dk/files/2775719/imm855.pdf [3]: https://pdfs.semanticscholar.org/b840/ae4b928964eff41206f89f...

oddly enough, I'd probably get more attention from border agents than my actual colleagues.

I wonder how long they'd put up with my ramblings about memoization and search optimizations before they let me through. :P

you aren't alone.

recently, I was constructing a small query engine based off of Prolog, a language which I have never delved into the internals of.

the rewarding moments were when it worked. I didn't work off of any documentation, only by thinking how I'd design something similar. going "from scratch" is incredibly rewarding because you start realizing that some parts of your thought are based on well-trodden ground. things start to light up.

I'll never get tired of that style of work.

the mice ate deer meat, I wouldn't call that "cannibalism". the fruit flies and the yeast, though, I would.

title should be "The Fight to Fix Symplectic Geometry".

the answer is "the one you've heard of/touched upon first", or "the one you're familiar with", or "the one you're comfortable with".

typically, those new to programming have written in some language prior. it's usually just a few lines, but it's enough to get them hooked!

encouraging them to explore what they've already touched upon gives them something to latch onto. they presumably already had the tools set up, so what's wrong with continuing?

I'd question why it wasn't GitLab but after the recent outage it would somewhat be in bad taste. :P

what exactly was Python using before/where was it hosted? all I can find are the source archives on python.org. I'm assuming this wasn't a hard transition but I'm genuinely curious as to their development strategy regarding distribution of source.