1,185 karma · joined November 3, 2010
[ my public key: https://keybase.io/haldean; my proof: https://keybase.io/haldean/sigs/b8iMYgBztqHNxdzpE22mUbizveJMjo8AbBnxJimUpIU ]
> All the questionable contact importing practices. All the subtle language that helps people stay searchable by friends. All of the work we do to bring more communication in. The work we will likely have to do in China some day.
https://www.amazon.com/Laptops-External-50000mAh-Portable-No...
Google around for external laptop batteries, they make some really big ones.
I'd guess that this is because the fastest way to compute a precise silhouette of an arbitrary shape (like quadratic surfaces) is to do a ray test for every pixel that might hit the surface. You could project the surface onto the image plane to get boundary curves, but (a) determining the curves that make up that silhouette is a complicated geometric process that's prone to numerical error in weird edge cases (of which there are lots) and (b) once you have the projected curves, you still have to actually shade the interior, which require you to project back onto the original surface to figure out the normal, texture, etc. At that point, you're essentially doing little ray tests for each pixel anyway, so why not just raytrace the whole thing? The global illumination approximation is much much better with raytracing, and modern GPUs can do it real-time.
By the way, modelling everything as an analytic surface rather than as a discretized polygon mesh is called "Boundary Representation" or b-rep, and it's what's used in solid CAD programs that engineers use, like Solidworks or Inventor. Engineers and designers like analytic surfaces because they have "infinite" resolution, but even those CAD programs almost invariably polygonalize b-rep to a mesh and then render the mesh, because it's expensive to hit-test all the surfaces involved; computers only recently became able to do that fast enough for real time interaction, and most CAD programs are old old old.
Time tracking and invoicing already takes up a bunch of my, well, time, and to be honest I'm not willing to just try another one out for a bit without seeing more of how it works. More information on the landing page would be a huge start.
> But ever since Pascal, the language aspect has been almost secondary to Wirth's work. Modula(-2) and Oberon both came out of larger system-level design projects that simultaneously also developed workstation computers, modular operating systems, and suites of innovative application programs. Unfortunately, these other important contributions were overshadowed by the programming languages they were associated with, and hence never received the recognition they deserved.
Oberon was both a programming language and an operating system implemented in that programming language. Much like LISP machines, the boundary between programming language and operating system is fuzzy.
> The bill also would prohibit an employer from seeking salary history information about an applicant for employment and would require an employer, upon reasonable request, to provide the pay scale for a position to an applicant for employment.
They're not allowed to try to find out from someone else, either.
https://leginfo.legislature.ca.gov/faces/billTextClient.xhtm...
convert -colors 16 Ilker_fast.png Ilker_tiny.png
pngcrush Ilker_tiny.png Ilker_out.png
Total page weight is now 15kB, 0.2% the size of the original page. Incidentally, that ratio is about the same as the ratio between the original page and the entirety of the game Overwatch.The page is 2.3kB on the wire, and the single other request it makes (for the image) adds another 70kB. Taken together, this is a two-order-of-magnitude decrease in page size, with exactly the same content.
Every byte is sacred! This webpage infuriates me.