jheriko

59 ms·

631.
by jheriko 11y ago
it wasn't the dick waving bits that drove progress. it actually postponed it in many areas... that apollo program was damned expensive relative to the technology that came out of it. a gigantic vanity project. that whole man on the moo
632.
by jheriko 11y ago
if you are interested read some stuff on the subject, there is loads of it around... ice is a sort of equivalent to rock beyond a certain (not as far as pluto by a long way) distance from the sun. astronomers have a funny idea about what th
633.
by jheriko 11y ago
how would gravity do this? orbital trajectories are in free fall... tidal effects are all that are left and they are huge, smooth gradients, not tiny highly variable things of the sort that could create surface features like this.
634.
by jheriko 11y ago
the quality of the code shakes my faith in whoever debugged or fixed anything to have not introduced more bugs as they did so.
635.
by jheriko 11y ago
there is no excuse for this. its trivially refactorable into something easier to maintain with less ifdefs if you are willing to include/exclude files by platform. (and if not, just wrap whole file contents in single ifdefs) this is a
636.
by jheriko 11y ago
i never said you can't. i just said you could...
637.
by jheriko 11y ago
they held back a toolchain for android native development for ages, but yet quite obviously used one to build the OS itself. its still a 3rd class citizen, despite being the backbone of the platform.
638.
by jheriko 11y ago
> Writing a single shared library for different platforms makes sense i've always taken this approach... like since the 90s, although not necessarily a library, but shared code. there has always been a way to do this thanks to the u
639.
by jheriko 11y ago
very good of apple to not reject it for the terrible ui... well done though its good to see new tech making its way into the walled garden of the app store.
640.
by jheriko 11y ago
> You can google a quite specific problem and more or less always find a result usually when i have to resort to finding someone else's solution i find nothing. its probably a 70/30 or 80/20 split. when it comes to low lev
641.
by jheriko 11y ago
not if you had no internet. :) i had help files and terrible books. :P
642.
by jheriko 11y ago
> Currently you look up on google the error message the compiler gives you this makes me afraid a little. although given the style of your examples i can imagine you have just not had a problem just because of using simple and permissive
643.
by jheriko 11y ago
if you were a late comer to those days it was amazingly good. the help file from qbasic got me started down a path that didn't end, and getting a visual basic with msdn on cd was even better... it makes me sad when i see the msdn today
644.
by jheriko 11y ago
wasting time remembering the unimportant fine details is a sign of a bad programmer imo. good programmers use software to make themselves better and google is a very reliable alternative to excessive memory (but not understanding, or proble
645.
by jheriko 11y ago
there is a lesson here. think about the problem before researching it. i've seen a lot of terrible algorithms come from people reading papers which provide solutions that are worse than they could come up with themselves. they may even
646.
by jheriko 11y ago
why not use an array of structs as the program, with a function pointer and the parameters stored in the struct? the instruction pointer is then an index into that array... the functions implement the opcodes and the archetecture becomes mo
647.
by jheriko 11y ago
exactly :)
648.
by jheriko 11y ago
i saw the thing on twitter earlier. what i don't get is why not ask the question of what that means? its such a simple problem once you know... and irl you don't know everything, if your interviewer expects it then you reject them
649.
by jheriko 11y ago
> It's all mindless cargo-culting, and it doesn't actually work amen.
650.
by jheriko 11y ago
are we reading the same article??!?! the content is quite good but the layout, colour, animations etc. are a mess.
651.
by jheriko 11y ago
its more that its not about writing code to be testable. its about writing code well to start with for n reasons.
652.
by jheriko 11y ago
+1 stb_image.h it uses a good interface for an image loading library, something nobody seems capable of even in the "good ol' days"... just a shame it doesn't support more of PNG (16-bit channels would be nice, and suppo
653.
MODO 901 free trial available(thefoundry.co.uk)
2 points by jheriko 11y ago|0 comments
654.
by jheriko 11y ago
this just falls out of writing code cleanly and properly. if you are doing something so complicated with inputs and outputs thatit becomes unclear what is happening and where things need to go in and go out then you just haven't used e
655.
by jheriko 11y ago
let me see if i can find a shit to give about that...
656.
by jheriko 11y ago
i think linux/mac systems default to UCS-4, certainly the libc implementations of wcs* do. i agree its a flawed idea though. 4 billion characters seems like enough for now, but i'd guess UTF-32 will need extending to 64 too... and
657.
by jheriko 11y ago
hmmm... wait... UCS-2 is just a broken UTF-16?!?! I thought it was a distinct encoding and all related problems were largely imaginary provided you /just/ handle things right...
658.
by jheriko 11y ago
i can't help but wonder if this has been tested vs. just letting the os virtualise memory for you... i'm assuming yes.
659.
by jheriko 11y ago
> If the readership on HN is plugged into the startup scene, hiring mediocrity is not fine. i'm curious what this means exactly. having worked for startups in my area of things (graphics, games) i can say that 99% of the startups i
660.
by jheriko 11y ago
this is a beautiful observation, and very true imo.

More ›