|
Not to anyone who reads my code. 
|
|
|
|
|
Apple's built a great marketplace for apps, and with the popularity of the iPhone and the iPad, it's created a huge userbase of people ready to spend money to support them. Right now, there's still a fairly large wall of knowledge required to put an app together. But with new interfaces like ScriptKit, we're moving closer and closer to the point where anyone with a really great idea will have the chance to drag some code together and make something really useful and cool. Point-and-click programming is getting better and better.
|
|
|
|
|
and so it seems coding (if even needed) gets easier, but much more expensive... 
|
|
|
|
|
Google has enjoyed a considerable head start on the mobile-mapping front, but Apple and Microsoft haven’t been idle. Both companies have licensed data from a number of services to flesh out their competing map offerings in an effort to bolster their respective phone platforms and chip away at Google’s dominance. But there’s more to a map than getting users to and from work: We rely on maps to figure out where we are, to find new places, and to plan trips far beyond our local haunts. Here's a look at which mapping service offers the best features and functionality. We got a full tank of gas, one bar of cell reception, it's dark... and we're using maps from...
|
|
|
|
|
A new security hole has been discovered in Microsoft’s product activation process that allows pirates to get a free legitimate activation of Windows 8 using the current Windows Media Center upgrade promotion. Pirates have been having a harder time with Windows 8 because Microsoft no longer allows volume keys — each Windows 8 activation requires a unique key. However, a hole was discovered that involves using the KMS (Key Management System) , and then applying the freely available Windows Media Center upgrade on top of it. ITSNOT-THAT-EXPEN-SIVE-JUST-BUYA-COPY
|
|
|
|
|
Thats right it is nor really expensive
BUT !
I think Windows 8 is only needed if you have an Touch-Sensitiv-Display or Laptop or Tablet or Mini-Tablet or Ebookreader or ...
if you don´t have such a "thing" well then you dont need Win8 cause APPS look really really ... BAD! why Fullscreen ? WHY ?
and what about all the clicky-clicky till i shutdown my PC ... just pull the damn cable ... 
public class HelloWorld {
public static void main(String[] args) {
System.out.println("Hello Reader!");
}
}
|
|
|
|
|
Given the recent controversy around the design of Windows 8, it’s interesting that Jensen Harris, one of the people behind the Windows 8 design recently spoke at UX Week, and that his presentation is available online for all to watch. If you’re concerned about this topic, you’ll want to check it out.... His central argument is that while each Windows revision has been familiar to users since Windows 95, people are willing to change if you give them something better. Resting on familiar is the way to mediocrity.
|
|
|
|
|
I, like so many thousands of other entrepreneurs, developers, IT professionals, and businesses small and large have been able to support our families because of Lotus products and their value to the businesses who rely upon them. Then, last week, IBM's Ed Brill quietly announced on his blog the sunsetting of the Lotus brand. Notes and Domino will be with us for quite some time (after all, so many companies rely on these workhorses), but the Lotus brand is officially now one with history. I'd rather keep the brand and lose the software, but maybe I haven't used it enough...
|
|
|
|
|
I know there are a lot of people who made a lot of money supporing Lotus Notes. I avoided it. Don't know if Sharepoint if better or worse, but think they are similar. It is also a pain to work with, and people make lots of money supporting Sharepoint.
|
|
|
|
|
|
|
I do not understand the message!
|
|
|
|
|
See the thread posted just before yours.
|
|
|
|
|
Looking over the link, it seems to actually indicate that they are equivalent.
|
|
|
|
|
If you see some of the comments, which I agree with, the extra capabilities of the List seems to be the deciding factor for many.
|
|
|
|
|
[ramble]
Regardless, I still have a sense of distrust when using Linq, and I'd be rather loathe to use it for large (more than a few hundred) records, and I imagine that if the expression (if your processing data from a database) will still run considerably faster in native SQL on the database server itself. Plus, debugging those IEnumerable<T> and friends collections is rather impossible unless they're converted to List<T> first. The debugger definitely needs to be more helpful! That said, Linq (and lambda expressions) are definitely very sexy for certain things!
[/ramble]
Marc
|
|
|
|
|
I try to keep to the LINQ Enumerable, but definitely do not like it. The advantage and disadvantage of the LINQ Enumerable is that the LINQ statement is only executed when it is needed; That can cut down memory, and processing. Of course working with them in the debugger can be painful since you have to physically cause the LINQ to be executed with the Expand results. Also, after a while can no longer even get the LINQ to execute. I therefore will sometime convert to a List when programming so that debugging is easier, and when I am finished, convert back. I have also found that I need to convert to a List when working with EntityFramework because errors cause once out of the Object Context. I also have found that working with WPF binding, it can be advantageous to go with a List.
|
|
|
|
|
It makes sense that if theres an array and a list of the same type that there would be some additional overhead because of the added benefits of the List type. I like that linq gets rid of my for loops with lots of nested if statements.
I have been using resharper from jetbrains.com to rewrite my for loops with nested if statements and boolean logic to LINQ and now I can write my own basic lambda expressions and im finding more uses every day.
|
|
|
|
|
I think most experienced programmers really like LINQ. It definately cuts down on a lot of code. However, and you have obviously learned, there is a significant learning curve. I have also learned a lot from resharper.
|
|
|
|
|
if data will be changed later (insert,update,or delete) you prefer to use ToList().
|
|
|
|
|
Obviously a ToList is a lot more flexible. Since the performance is slightly greater as a small cost in memory, ToList seems to be the better choice, even if you will not be needing to make any changes. I can think of very few times it is worth do ToArray.
|
|
|
|
|
.NET applications sometimes need to work with external processes. In some cases it is necessary to wait for those processes to generate results and exit before the .NET software continues executing. Waiting in this way is possible using the Process class. Here's how it works.
|
|
|
|
|
That's news? 
|
|
|
|
|
Nope, though I think it's an interesting tidbit and it's news to me. I've been working with .Net for the better part of a decade and this is the first time I've seen such a thing.
Of course, I probably would have found it if I'd been looking for it, but this may spark some ideas of how I can use something like that.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
