Showing posts with label Design-ID. Show all posts
Showing posts with label Design-ID. Show all posts

20091109

Homeworld Cataplasm Online

I've been spending quite a few hours dusting off years old pieces of design, mainly EVE-related stuff, since the announce of their December train wreck expansion… My most recent WTF? moment — and the ensuing drawingboarding of ideas about tactical maps and in-game intel management got me thinking: am I sketching a full-featured wargame, here ?

…and more importantly, does anyone remember Eschaton Online, a space-themed wargame a few years ago, that revolved around the notion of multiple play modes, ranging from god's eye strategy to in-cockpit dogfight ?

If you've played it and have opinions to share about that, send an email my way, pretty please: I'm curious to know.

20090422

Steampunking the MacBook Pro…

Right about to get one of the 'new' unibody 17" MacBook Pro, I'm told these tend to run *hot*.


Looking at Apple's specs, the operating ambient temperature range for these machines is 10°C to 35°C.
Needless to say, I routinely run my laptops on the high end of these temps, if not higher, which is a good enough reason to be concerned that those figures may not just be a matter of CYA on Apple's part.

Add to that the double issue of battery life and dust buildup inside the machine, both of which are tied to how often and how hard the two fans at the rear of the MacBook have to blow on the CPU/GPU heatpipes' heat exchangers, and it becomes obvious that anything which can be done to improve the cooling of this laptop by other means is a GoodThing™.

[Speaking of which, I'm not entirely sure how much of the air intake is done from the rear grille and how much is dependent on semi-improvised various holes such as around the keyboard, etc.]

Since I want to keep the drilling through the MacBook Pro chassis to a minimum of roughly zero (and it's not like there's much room to spare inside the box anyway), the back of the display casing seems like the best place to hook up some external cooling apparatus.


Yet before I even begin to worry about where the heck 'plate' type heatpipes can be procured, or how to build a small thermosyphon, I'll have to figure out the first and so very weak link in my thermal chain, ie: how to extract the heat from the 'cold end' of the factory heatpipes, and bring it to the 'hot end' of a back-of-the-display thermal circuit ?

The wiggle room between the internal heat pipe and the unibody shell is about 3 millimeters at best, and right next to the rear grille, so I figure a sheet of copper attached with clips and connected with thermal paste to the 'cold end' of the factory heatpipes can get me out of the chassis without sigificant adverse effects on the factory cooling system.
…yet from there I still need to work my way around the bottom of the display (which rests inconveniently below the topside plane of the main chassis) to reach the 'hot end' of the external heat dissipation circuit.

And no, hard plumbing is not an option, the display must still be able to open, adjust and close with the external cooling system mounted on, so the thermal bridge better be flexible.

Ideas ?

[See here for an in-depth look at the innards of the 17" MacBook Pro Unibody.]

Glaswegian Computing.

I'm currently looking into options for an unpowered and silent yet efficient cooling system for a mid-to-high end gaming rig.
At first, I looked into heatpipes and/or thermosyphon based designs, but I recently stumbled on an old experiment, and it got me thinking.



Yes, at the uncanny crossroads of Scottish cuisine and Xtr3m3 nerdiness, people figured deep-fried computing was an operating concept, provided the tub is see-through.
Seriously, follow the link, I'll wait…

The quick and dirty cooking-oil-in-a-tub proven surprisingly solid, especially on the noise reduction end of things, which is kind of a big deal for me.
I also like the elegant simplicity of a pure convection liquid cooling system with zero pumps or extra power requirements.

The main limitations of the oil-immersion model (besides the yuck factor when adding extra RAM) seem to be the potentially harmful capacitance and corrosive characteristics of cooking oil, but provided a similar fluid without those drawbacks can be substituted, this approach has real potential.
Oil-like liquids, despite being less thermally efficient, are especially attractive as they don't evaporate as easily, which fits the general less is more angle I'm going for.

It would seem practical enough to build a kit based on a ready-made durable container, where the motherboard and PSU would be placed near the bottom, while everything that needs to remain easily user accessible such as drives and I/O connectors could be installed above 'sea level'.
Some passive funnels could also be mounted inside the cooling pool to boost the convection cycle.

Provided the side walls of the containers were made of acceptably transparent material, plexiglass style, and that two or more (non-soluble with each other) fluids of different densities could be found (that fit the conductive/capacitance/corrosion bill), a 3GHz lava-lamp becomes a distinct possibility.

Obviously the one big technical bump is finding the right fluid(s).

Any ideas ?

20080417

Zulu Time 4tw !

Seriously folks, as if DST wasn't stupid enough, do we really have to combine it with the retarded concept of time zones to make things even more uselessly confusing ?

One would argue having hours all fuzzy and mixed up around the clock has a redeeming value, would it contribute to raise awareness about the notion that time is not, in fact, a constant and frozen dimension, but c'mon: grab anyone at random in the street — not on campus, you cheater ! — and ask them how switching the clock forward one hour every spring makes them feel about their LightCone.

Chances are the answer will be something akin to "Huh ?", or "Go away, you pervert !", depending on gender/age differences between the guinea pig and yourself.

Not only are Timezones stupid in essence, when no one sets their clock by sundials anymore, but they are botched beyond repair. Check the map, and tell me if it makes sense to you...

As national borders erode in favor of continental (global) and regional (local) spatial references, clinging on a literal translation of sovereignty from map to clock is about as relevant as the defense of flat earth theory, or the selection of rulers based on physical prowess.
...hold the presses, does "best hair" count as physical prowess ?

Moving on.

Zulu to the rescue.

That's an easy fix: let's all switch once and for good to Zulu, GMT, UTC, UT1, TAI, however you want to call it, and be done with that.

No matter where you go, then you are: no more clock fiddling, local time confusion, longitudinal discrepancies over nonsensically expanded/shrunk timezones. US east-coasters would have diner around 23.00h, just like they do now, only their clocks won't be blinking stupidly on 6 PM anymore, and it will still be about breakfast time in Osaka, just like today.
[And yes, we would take the opportunity to get rid of the dumbalicious AM/PM notation, as it really, really wouldn't mean squat anymore.]

If people can adjust to DST twice a year — a change just big enough to be unsettling for a couple weeks every time it happens — odds are pretty good they can adjust to a one-time, however severe change of display on their wristwatches.

Maybe the transition could be helped by going for dual-display of *old* and *new* time, while I suspect it could be more a drag than anything.
Alternatively, clocks could be upgraded with a fourth hand, coupled with geolocation, that would point solar noon for your current locale, and give a feel for one's "when" in the day.

That would be cute, and sell a lot of wristwatches, gotta love it.
[If someone knows how to hack a google gadget for that, eternal love shall ensue.]

Why UTC and not InternetTime ?

Short answer: because Swatch's iNet Time is a proprietary time.
Long answer: because Swatch Internet Time is just as ridiculously stupefid as the short answer above hints.
  • It's locked on Biel, Switzerland (no kidding), and not even accurate at that ;
  • It substitutes an arbitrary unit everybody is used to for another no one will get used to, as it doesn't fucking divide (because-we-can type of design flaw) ;
  • who wants to to mesure 2.31481481481 friggin beats to properly cook an oeuf à la coque, anyways ?
Case closed, as far as I'm concerned.

Wrapping up

Zulu is good because it's already a standard for time-critical applications, like airlines, high-sea navigation, and basically anything that has a non-cosmetic use for timekeeping.
Also, most people who routinely relate or travel to distant locales are already up to speed on their relative position to UTC.

As an ancillary benefit, coming to agree on giving each other the time of the day could be a nice first step towards acknowledging we're all more or less on the same boat.

Holy Carpaccio, Melissa: how campy can I get with punchlines ?