1,332 karma · joined February 28, 2014
I'm suggesting it's feasible but not necessarily perfect and when it does go boom, which it does when you have 100 million HTTP hits a day, you need to be able to find out precisely where it went wrong. LINQ makes that damn hard:
NullReferenceException
Company.Product.Assembly.Namespace.Type.Method() +14
...
When line 14 has 22 dereferences then you have no idea why it broke.A lot of people say this stifles creativity and is boring but the productivity is off the scale. I've built things that would cost £50000+ in dev time and licenses and take 3 months in .net in a couple of days in Java without spending a penny (reporting, messaging, email processing, document scanning, parsing, bulk processing, ETL, matching, logging). This is because someone already did the leg work and released it with an open source license meaning no license cost. Not only that, the ecosystem, Unix based deployment platforms are all easy to automate so jobs only get done once and stay working. Sure you can throw out an ASP.Net MVC web app quickly but that's the easy bit.
We can put £500,000 a year back into open source projects through time investment and donations if we replace .Net and still do better than break even on the dev cost.
I still write C and don't hang myself because it doesn't have generics!
collection.Where(s=>s.Transaction.Amount < 100).OrderBy(s=>s.Name).Single();
I'll let you debug the intermittent NullReferenceException that threw in production with no PDBs...I've used most of the above. ServiceStack was pretty good but nothing in comparison to Jasper which has much better documentation, a cleaner architecture, stable migration notes and better performance. Look: https://jersey.java.net/documentation/latest/index.html
NancyFX I haven't touched.
NHibernate is a buggy behemoth with a learning curve from hell. It doesn't scale well with project size (we have 2000 tables of which about 500 are NH mapped "model-first") and it stinks. The SQL generated is terrible, it's impossible to debug when it goes wrong other than sift through 50Mb of log4net DEBUG level logs. To add insult to injury, the LINQ provider is so buggy it's like programming with a hand grenade. I've used hibernate in java and NHibernate isn't even a tenth of the way to the maturity and reliability.
Dapper - I really like Dapper. I have used it for data transforms before. However it doesn't play well with low trust as it uses IL emit.
OrmLite - see ServiceStack.
Not bad choices - just choices I either regret or had to make because the whole ecosystem is amateurish outside of Microsoft and unstable inside of Microsoft. Sorry.
I agree with you though - its a PITA.
As for me, because I'm in charge of the migration. When its gone I'm not even going to go to the funeral.
Not one of the above has actually improved the product we produce and are all reactionary "we might get left in the shit again" changes.
I'm really tired of it now.
I have East German parents and they lived on that stuff until the wall came down.
I can't see it selling here.
You're complaining about WDM audio. There's built in WaveRT and external ASIO stacks as well. The latter has become the standard on Windows for professional audio and is direct hardware access.
USB audio devices are and aren't polled. The cheap ass speakers and stuff are but anything $20+ are buffered raw device access.
I can get 8ms out of a Windows 7 laptop with ASIO over USB that isn't even tuned. My Korg Triton Studio manages about 4ms and that's seriously high end kit.
Everyone I know has a sub $100 USB interface hanging off their machine and swears constantly at the latency and wishes they'd just stuck with ASIO on Windows...
Personally I still have a workstation...
As for the iPods they sound horrible. The latest line of nano has noticeable noise on the outputs.
1. They actively monitor your connection to be able to determine whether or not you have "infringed". This has non legitimate utility.
2. They are building a mailing database which whilst is under a mild agreement may in the future be made available under different terms.
So this is not a win, it's a tragic first step towards what we don't want.
They obviously will have to develop a heuristic for suspicion and store suspects somewhere. If that list becomes available by accident or court order then it puts people at litigation risk. Unfortunately despite guarantees supposedly mandated by law, if you're confronted with a case then you're screwed either with respect to costs or defense.
I would suggest people start moving to Andrews and Arnold or a similar smaller ISP immediately.
It's impressive but no more impressive than navigating a 4 million line software product intuitively...
I didn't realise what a rip off they are until I started driving around the city myself regularly with Google Maps which to be honest with traffic aware routing destroys "the knowledge" instantly. Black cab drivers know how to make cash, not the most efficient journeys in time and money. That meter hurts you badly.
So they'll cause some chaos; good for them but it'll raise more awareness on the issue and hang them faster.
More competition is required in this sector for the passengers.
What you want is an illusion of privacy. The two are vastly different.
If privacy is required, I leave the handset at home and get on my bike. There is no hiding unless you turn it all off.