|
They missed an anti-pattern: Farting.
|
|
|
|
|
The European Commission is issuing antitrust charges against Apple over concerns about the company’s App Store practices. It just takes a complaint to the EU to punish Apple? I need to make a few calls.
|
|
|
|
|
They've created a web-based experience you can access on your computer that takes advantage of machine learning and computer vision software to make the process fun and easy. Think of it as having a free ASL teacher. "I had now the key to all language, and I was eager to learn to use it. "
|
|
|
|
|
Load your vbp without migration and continue working with your VB6 projects. Bring your VB projects to 21th century with 64 bit support Because I know you were looking for it
|
|
|
|
|
"It wants to be the true VB7 that never existed. And the compiler and runtime libraries will be open source."
Unicorn, Unicorn, Unicorn
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
I missed the bit were it also makes breakfast and rubs your back. 
TTFN - Kent
|
|
|
|
|
Good for him. I reckon a lot of people (including people in corporate environments with some money to spend) will be pleased to see this.
I can see the same sort of thing being needed for VB(.NET) soon too. In a way it already is.
VB.NET is already falling behind C# features due to Microsoft's odd dislike of and disinterest in VB. One feature are local routines which C# has but VB does not. Why doesn't VB have them? Apparently because they aren't seen as useful in VB by the Microsofties in charge. What a bizarre idea. If they are using in C# then they'd be useful in VB.
I've mooted trying to write a VB-to-C# convertor. This is not as difficult as it sounds, especially as the C# and VB compilers are open source now. It wouldn't be compiling VB direct to IL but the parser code would be useful as a base to be able to reliably parse VB (including LINQ and XML literals). Outputting C# is really not difficult from what I can see.
This would also give the software the ability to add new features to this new-VB in an upwardly compatible manner to more closely match some of C#'s recent additions.
The biggest effort would not be the VB-to-C# transpiler itself but would be building a VS addon to support editing the new-VB from within VS and automating new-VB-to-C#-to-IL transpile/compile process, as well as debugging.
Economic sustainability is the question. Would there be a paying market for it? Carles Royan thinks so with RAD Basic and he has designed what looks to me like a sustainable licensing scheme with open source entry points.
|
|
|
|
|
markrlondon wrote: VB.NET is already falling behind C# features due to Microsoft's odd dislike of and disinterest in VB
It's not odd in the sense that VB is heavily maligned by masses of MS-centric developers and others. So Microsoft is probably reacting to that, to an extent. Didn't they recently say it was the end of the road for VB or something?
Personally, although I prefer C#, I've also done a lot of both VB Classic and .NET. I don't really get the hate. There's much worse stuff out there!
Kevin
|
|
|
|
|
For better or for worse, this project is on track to fail to meet it's funding goal by massive 72%:
RAD Basic: a 100% compatible Visual Basic 6 solution by Carles Royan :: Kicktraq
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
Founder says the infinityQube operates at room temperature and can integrate with existing high-performance computers. Good news for sales people?
Because I hear that the death of a salesman is a sad thing
|
|
|
|
|
IT decision-makers are embracing Secure Access Service Edge, or SASE, to simplify and centralize the entire process of managing both networking and security while saving money. Self-Addressed Stamped Envelopes?
|
|
|
|
|
Like so many other companies, Google is getting ready to welcome thousands of employees back to the office, while trying to figure out how to make the office a safer, more functional, more collaborative environment for a hybrid future. How about bouncy castles?
|
|
|
|
|
There are plenty of times in my career when I’ve stored a boolean and later wished I’d had a timestamp. There are zero times when I’ve stored a timestamp and regretted that decision. Is it time?
|
|
|
|
|
Echoing an earlier report on the popularity of ASP.NET in the .NET/C# tech stack, a new survey from the .NET Foundation finds the web framework dominates the ranking of app models used by respondents. That web thing might just stick around
|
|
|
|
|
Why are even experienced software engineers drawn to shiny new technology like moths to a flame? A personal account of learning the hard way: You have to balance your curiosity with your business’s goals. All at once, and only when the project is already late?
Or is that just my managers?
|
|
|
|
|
From a graphic in the article: Trough of disillusionment
My new catchphrase!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Oh Great Ghu, yes!
My personal trough of disillusionment with a new technology was achieved in the very early 2000's. I thought Windows COM sounded like a great way to construct a plug-in architecture for our application. I got it working - finally. This was despite piss-poor documentation and non-functional samples from Microsoft. No one building COM applications used the same vocabulary, or even defined terms in the same way. I still don't know what the ![Elephant | [mastadon]](https://www.codeproject.com/script/Forums/Images/elephant.gif) a COM moniker is for. Often there were three ways to do a particular thing, and it was only the fifth method you tried that actually worked. If I'm being honest, I believe I spent an order of magnitude more time developing the COM plug-in mechanism than if I'd used something based on DLL's and well-known entry points.
This application is still being maintained today, and is still using the plug-in architecture. I've refactored the code sufficiently that the plug-ins are fairly consistent. Creating a new one means copying an existing one and changing some GUID's in a header file and identifiers in the source files. Yes, it sounds like copy-paste programming. It's not done out of ignorance, but out of the knowledge that this method guarantees that all of the COM bits and bobs are in the right place and pointed in the correct direction.
Software Zen: delete this;
|
|
|
|
|
Quote: piss-poor documentation and non-functional samples from Microsoft
True! Good for you! I'm not sure if I'd have the gumption to tackle something like that. I kind of miss the days of assembly programming using the old 68HC11 from Motorola, great documentation, good examples.  The good 'ol days.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
jeron1 wrote: I'm not sure if I'd have the gumption to tackle something like that
In hindsight is wasn't gumption so much as foolish pride. Early in the project I decided this was A Good Idea, despite other folks being skeptical. I had to prove them wrong, you see. It was also written in C++ using MFC, which meant COM was a couple of orders of magnitude more difficult than in the nascent VB or C# world.
I learned my lesson, however. A new product started in 2008 has a similar plug-in approach. This one was implemented in C#/.NET using a tiny bit of reflection during startup to enumerate plug-ins. Vastly simpler and far fewer problems outside the application.
One of the benefits of becoming A Wise Old Head is learning when to cut your losses, admit your mistakes, and try something else.
Software Zen: delete this;
|
|
|
|
|
Gary R. Wheeler wrote: One of the benefits of becoming A Wise Old Head is learning when to cut your losses, admit your mistakes, and try something else.
Wise words indeed. 
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
There is only one right way - let someone else go for it and then read about their horror stories. 
|
|
|
|
|
 The correct answer 
TTFN - Kent
|
|
|
|
|
i see dead javascript code...everywhere...
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
“The reality is that Google has fundamentally sucked most of the oxygen out of the opportunities for people who create content to actually earn a living through advertising,” said Smith, who is Microsoft’s president and chief legal officer. In this crazy, topsy-turvy world, it's nice to know that some things will never change
|
|
|
|
|
Driven by hunger, a fox tried to reach some grapes hanging high on the vine but was unable to, although he leaped with all his strength. As he went away, the fox remarked 'Oh, you aren't even ripe yet! I don't need any sour grapes.' People who speak disparagingly of things that they cannot attain would do well to apply this story to themselves
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
