HN user

jbester

123 karma
Posts0
Comments59
View on HN
No posts found.

The original 747-100 /was/ spacious on international flights, the upper deck had a lounge and a piano. This wasn't due to some bygone era where passengers weren't treated like cattle, it was due to the underpowered JT9D-3A engines.

Without sufficient power, the airlines lowered the amount of allowed weight on allowed on international flights and thus the seats had better spacing. Later models starting form the -200 model had more powerful engines so they crammed in more passengers - both in coach and in first class.

Keep in mind, ITAR and AECA regulations are concerned with export weapons and weapons systems to non-US entities. The munitions list (USML) includes everything from guns to airplanes. The regulations themselves go well beyond physical assets and include related software, documentation and design drawings. It is likely DEFCAD, if they survive any fines, could reopen if they can somehow verify the downloader does not require an export license.

This is the same set of regulations Robert Gates famously complained[1] restricted the export of F16 spare parts from the US. This platforms has been widely exported and this regulation applies to non-weapons related components i.e., canopy latches, flaps, etc.

[1] http://www.nytimes.com/2010/04/21/world/21export.html?_r=0

Bitcoin hits $200 13 years ago

Not sure I buy either of the metaphors. Silver has industrial, scientific, and commercial (i.e., jewelry) applications that create demand and use the commodity. Bitcoin, on the other hand, does not. It's just used as a transitional currency.

Historically, spikes in income inequality have been a harbinger of a recession - the theory is it can indicate misapplication of capital. In that investment income is outpacing growth in the underlying economy (using worker's income as a proxy). Not sure how true it is in the era of multi-national conglomerates and outsourcing.

Technically, he's charged with espionage and giving aid to the enemy. With the stated motive of "sparking a public debate" regarding current war policy, a more targeted leak would have achieved the stated goal, in line, with, say, the pentagon papers or the AT&T/NSA leaks or even the his own later leak of the gun-cam video.

I have a hard time believing the flagrant and wanton release of material was and is not suicide by Court Martial.

In 2011, Wired posted[1] the transcript of conversations between Bradley Manning and Lamo, the man who informed on him. It's an interesting read and gives a window, albeit a small one, into his mental state and underlying motives.

I would not consider the transcript complimentary, it does not portray a high-minded, moral crusader. It portrays Manning, the depressed, confused, trans-gendered person, acting out against the Military Establishment.

[1] http://www.wired.com/threatlevel/2011/07/manning-lamo-logs/

Light on dark can be really hard to read for anyone with a pronounced astigmatism.

The background color bleeds into text dramatically lowering the contrast. On computer displays, black on pure white can cause the same issue to a lesser effect. I find black on a pale color is optimal.

It's neat. I noticed a couple of subtle bugs.

1) The code assumes both the client and the server have the same endian. This can be issue since a uint32 is used for both the synchronization code (BCP_CODE) and the port. This can easily fixed with htonl/ntohl conversions.

2) it assumes both the client and the server define int to be the same size (may or may not be true based on compiler/processor/OS combinations). If you use stdint definitions, this typically won't be an issue.

The proposal is to keep LTS releases - but lose the interim releases. I assume after an LTS release you'd be given an option "upgrade" to the next LTS testing branch which give you updates until it that LTS is released.

I should add: the value proposition for mono is a bit bizarre.

On the server, typically mono is chosen because mono on linux is much cheaper than azure, or windows hosting (AWS, etc) therefore you trading slightly more development and setup effort for cheaper run-time costs.

For the phone/tablet market, you are doing the opposite trading money (monotouch licenses) to save development time and learning a new platform.

On the desktop, I think the value proposition is much less well defined. It depends alot of the mix of clients you are supporting.

Ximian has a plugin (http://mono-tools.com/) that lets you remote deploy/debug mono applications from Visual studio - it was free after a survey not sure if it still is or if it will be updated to vs 2012.

There are other tools sharpdevelop (for window) and monodevelop (all platforms) - but they are somewhat lacking. Sharp develop seems to slow down dramatically on large projects or WPF projects. Monodevelop seems to lag sharp develop in features and maturity.

GUI toolkits for dotnet are hit-and-miss. GTK# has the most traction and is cross platform - the documentation was lacking last time I looked. But, if you have a GTK background it may be a non-issue. Wx and QT bindings exist but I believe development has slowed down/stalled. Of course, there are OS X, android and iOS bindings that ximian sells. Unless you have a large existing c# code base it probably doesn't make sense to use them for greenfield development.

Server-side is where I think mono actually does shine a bit. Although you need to move out of the standard NetFX stack (i.e. WCF) to other open source libraries (i.e., ServiceStack). ASP.NET and MVC do run on mono - there are tutorials to deploy against apache or nginx.

As you can imagine there is some lag between mono and microsoft dotnet framework (see http://www.mono-project.com/Compatibility). The gist of it mono tries and succeeds keeping up with the framework but there are large holes with respect to .NET 3.0 (WWF, WCF, WPF). There was a silverlight plugin (moonlight) but much like silverlight new development has stopped.

.NET Micro framework is actually a different beast in that's it's close to the metal but it's not compiled to a specific architecture. The MF is a bytecode interpreter vs the mainline dotnet framework which is JIT'd or AOT compiled (with NGEN).

This approach gives a couple advantages and a couple disadvantages. Specifically, the advantages the debugging and reloading can be done extremely quickly, the bytecode is small thus giving a lot of functionality per the byte of storage space, and it's significantly easier to port from microcontroller to microcontroller. Downsides, it's pretty slow - typically the heavy lifting happens in the HAL/MF, and you can't write interrupt handlers directly in it - although you can indirectly via the managed driver interface.

If these work like they used to - the connector is used to sync the lock with the key machines at the front desk. It requires a reprogram if the master keys need to change (ie someone is fired), batteries die in the lock, etc. Additionally it provides self test info and obviously if you need to force it open (i.e. Maintenance may send the open command in case of reader malfunction). That's why the mechanical solution doesn't involve physical changes to the lock guts - just the housing.

Macon is a town with a large blue-collar population that lost most of the major industries in the last 15 years. This is part of a multi-pronged approach to get Foreign-owned companies to locate low-skill jobs in the city.

In python 1.X it was a function under the string module. This is maintained in 2.x but goes away in 3.x.

string.join(['1','2','3'], ' ') == ' '.join(['1','2','3'])