I slept all day.
after we left the place for a second time, I realized my tire blew out when I hit the curb or pole.
waited until 6am for a truck, cuz I couldn’t put the spare on myself cuz a wheel cover nut was broken, and I had no pliers.
so we got home at about 8am.
I slept till 7pm after being up over 24hrs.
eggs and toast tastes REALLY good when you haven’t eatten a meal in over 24 hrs.
I had a good time last night (the eve of New Years Eve). I’m so exhausted I hope I have some energy to do it again, albeit less, tonight.
It was fun talking about the merits of p/invoke with forgue. It was also good that we didn’t geek out too much since my wife was there.
Jeff Tickle is far kinder than me.
You are a very kind person. Your words are those of a bridge builder and someone who truly and deeply understands the freedom which linux brings to the table. You are giving Linus much respect and benefit of the doubt in your reaction.
I, on the other hand, like to be evil. I like to be a total jackass in response to statements made by a total jackass. Linus is dumb. Linus is one dumb SOB. He doesn’t get it. He released a toy 14 years ago which grew into an awesome tool for us all, but he doesn’t have any vision for bringing the toy the masses. I don’t think he ever did. Anyone who sees the freedom which linux gives to us all and turns it into an “us vs. them” scenario is a fool. Linus just proved himself to be one.
Do I really believe these things? No. Linus is a hero of mine to. It always hurts when we see our heros make mistakes. It hurts more realizing that they don’t realize they made a mistake. It hurts still more realizing that they may not have the capacity to realize they made a mistake or ever admit it. I throw my hand in the air. Linux is still mine to use. Thank you open source. What has change from Linus’s statement? Nothing. Thank you open source. The next versions of gnome will come and go. The next versions of KDE will come and go. Linus cannot stop it. All he (or anyone) can do is make comments. Sometimes people will make bad comments. That is all that has happened. The next releases will come and go and we will have better software regardless.
This is a note to anyone out there listening to Podcasts. Beware.
Any person with a mic and a recorder (both of which are on most iPods) can make a podcast. There are many podcasts made by people who really do not know what they are talking about. I’m afraid academic .net radio is one of those such podcasts.
I just listened to the first 21 minutes (the podcast stopped there, maybe they published it wrong?) of episode 3 of the academic dot net radio show podcast. I honestly think they got more things wrong than they got right when they were describing things. I commend that they want to produce something to help student. That is great. But what I heard is truly a disservice to anyone listening. From describing what .NET is to the differences between VB.NET and C#, they got it wrong. Describing web services and soap, totally inacurate. The description of COM was also totally inacurate. And when the described Mono and its shortcomings they said “talking to Databases and Web Services aren’t there yet” !!!!! WOW?!?!? I’ve never had any issue with Mono and either of those things. AFAICT the ONLY part of Mono that is any thing short of .NET 1.1 compatibility is the lack of Windows Forms and of course the MSMQ and WMI parts of the base class library. They really did not understand how the framework is different from the base class library, which is very sad. Anyone who has spend anytime with dot net should really understand that difference. Maybe I’m a little bit too much of a langauge buff and I like formal definitions, but they were so bad that they were doing a disservice.
So if you happend to read this because you searched for dot net or dotnet and podcast, please don’t listen to the academic .net radio show. Go back and listen to Dot Net Rocks from episode 1 instead. Wait until those academic guys from Canada get their act together.
Also, as someone who spent 8 and 1/2 years as a student at a university and 6 years working at one for a total of 10 years being involved in academia, I expect more from something, anything, which calls itself academic. There was absolutely nothing academic about this show. Elementary or beginner would be better words. That said, I truly hope that they get their act together and figure something out and produce worthwhile content. I think it is an important hole which does need to be filled.
My whipped ice dairy drink brings the attention of many males to my place of residence and/ or employment, and they declare that its quality far surpasses that of yours. Absolutely, it far surpasses yours. I could convey to you the recipe, but i would have to demand compensation.
From digg, this article highlights a 33 year old man who never developed. He is gettng therapy and experiencing puberty and soon he will join the ranks of the rest of men whom are driven by only one thing.
My thought is: Don’t do it!
Man, if I didn’t think about sex every six seconds like the statistic mentions I could be much more productive. If I wasn’t distracted every time I looked at, or remembered a “sexy” woman, I could write way more code. I’d contribute to so many more projects it is sick.
Of course, I never would have met my wife, so I’d be miserable. Oh well, nevermind.
XML is the replacement for bad oo models. Why do anything naitive xml? What are the gains? Nnne. Drawbacks? Speed.
This is a note I wrote myself while in a meeting with co-workers a few months back. At the time, I’d not used XML for much of anything as a programmer. Since then I have changed my tune somewhat. However, I still am of the belief that XML is still not the panecea that many make it out to be.
XML is NOT a trump card for all the other design methodologies. XML isn’t a design methodology. If you aren’t designing and you think it is OK because “we are using XML”, then you are doing something very wrong. (i.e. you are stupid)
You must know XML’s limits. Everything has limits. Know them. When you are using a DOM library and your 50MB XML file is taking 500MB memory and you plan to do this on every request to your webserver and handle 100 requests per second, then you WILL have problems, unless you have $$$$$$$$ for an awesome server. If you do have $$$ for an awesome server, give me a call, I’ll come make your app 100 times faster.
XML is in itself not the problem. The problem is of course people. People don’t understand, so they misuse; it is the same old issue. I’m not as crazy about it as these guys.
I just ran across ScaleOut StateServer which looks to be an ASP.NET specialized distributed memory server much like memcached.
It sounds like a great idea, but who wan’t to pay for such a tiny feature? It is tiny features like these that Oen Source has generally done a better job with vs. commercial software IMO. So, for ASP.NET, this could be a perfect point for Mono to provide yet another big value add over the Microsoft implementation. After all, memcached is already done. All that needs to happen is the application session state provider to be written which uses it. There is even already a Java API, so if one were very desparate, then IKVM could make it come to be usable in a very short time. Of course, being the looser that I am, I think I’ll go down the path of making it work directly with the memcached using the memcached protocol.
it would be sweet to google ones logs.
- discover to which package you want to open a bug report to;
- open synaptic
- locate on synaptic your packageif the package has the ubuntu logo besides its name, it means this
package is in the “main” repository. So, for now, the bug report must go
if the package does not have the ubuntu logo, it probable came from
universe or multiverse repositories. In this case, you must report it
into malone, launchpad’s bugreport tool.
1 1/2 cups flour
1/2 tsp salt
1/4 tsp. baking powder
10 tbs. unsalted butter
4-5 tbs. ice cold water
Cut butter into the flour, salt and baking powder until coarse crumbs. Add water 1 tbs. at a time until dough begins to hold together. Shape into a ball, cover in plastic wrap and refrigerate. When ready, roll into a circl on a well floured surface. Lay over mat pie, trim edges, crimp and bake.
**Roll out left-overs and sprinkle with parmesean and herbs for a nice savory snack.
1/2 stick butter
1/2 cup flour
1/2 tsp. salt
1/4 tsp dry mustard
2 cups milk
1 tsp. Worcestershire sauce
2 cups shredded cheddar cheese (preferably sharp)
In a sauce pan, melt butter . Whisk in dry ingredients and cook 4-5 minutes (forming a roux). Slowly pour in milk and Worcestershire sauce, whisking constantly until thickened. Add cheese a handful at a time, stirring continuously, allowing the cheese to melt through. To serve, pour cheese sauce over toast.
Yesterdays flame fest by yours truely mentioned that I found a bug in Mono.
The bug turned out to be not in XSD itself, but in System.Xml.Schema. As a result, I totally misfiled the bug, but no biggie, they had it all fixed up in no time.
Yes, they had the bugzilla bug all fixed up, and they had the bug fixed. It was fixed in well under 24hrs, possibly under 12, I’m not sure. All I know for sure is that it was damn fast response time.