Yes. PowerBasic. Since the original developer has passed on (Bob Zale), I don't use it for new coding. However, I have an extensive existing code base. Very fast compiler, very small generated exe's, and very easy to work with. But, I don't see any progress in a 64-bit nor linux versions so I've switched to Python for such things.
I had to use some python with vs code recently and for some reason it reminded me (in a good way) of working in qbasic with the little ide/debugger. The same kind of quick simplicity.
In short ...
too many people take themselves too seriously.
too many people reading the intent to malign from internet postings made by people intending to help.
We Americans are not lost because power is taken away from the Federal government. The states (or even more local authorities) should be in charge of this. Ask someone from sparsely populated northern Minnesota what they think when their cattle are slaughtered by wolves that are over-populated because people in the big cities dictate law.
The power to make law regarding wolves already belongs to the state, as grey wolves lost federal protection earlier this year.
Independent of that, ranchers are compensated for killed, wounded, and spooked cattle under the pay-for-presence program and similar. The rates are favorable to the point of being a cash grab, and there have been numerous cases of fraud where ranchers claimed kills that simply didn't happen.
Independent of that, the federal government has poured subsidies into ranching for decades, to the tune of about $30,000 per rancher per year. Even if they weren't compensated for lost livestock, on balance ranchers are far better off with the feds than they would be on their own.
But you don't hear about that because, frankly, the ranchers are spoiled rotten. When something benefits them they accept it without thought, and when it doesn't, well, they either howl in protest on the internet or outright take up arms against the federal government in one of the most poetic examples of "biting the hand that feeds you" which I can name.
I'm from northern Minnesota. I'm dead-set against wolf hunting and trapping and so are my friends from the area. The idea that wolves are "over-populated" up north is a laughable fiction.
Since we're on the topic of environmental issues in northern MN, one thing that has upset almost everyone in the area is Trump allowing foreign companies to start mining in the Boundary Waters, an area that is near-univerally cherished by Minnesotans for its undisturbed nature (including its wolf packs!).
If you're not a Minnesotan, don't try to speak for us. If you are a Minnesotan, I contend that your perspective reflects only a relatively small minority of us, even among rural northern Minnesotans (like my family and friends!)
It is more irresponsible to make a comment like this. People should write software in a language that A) can do the job B) they're proficient in. For example, I would much rather have a C program written by someone proficient in C than a C# program written by someone new to the language.
Yep, not to bash the author but just to show how easy it is to write unsafe C. First function i started reading i already found a memory leak within a minute: indexer calls dsplit which calls dcreatea which calls malloc, this value is never freed inside indexer or anywhere on the way down. It might be that the buffer gets shared with index so by coincidence it's eventually freed but the fact that i have to think so hard and juggle all those buffers in my head for such a simple function just makes my head hurt.
dsplit(), an even simpler function also calls dcreate() which allocates memory into the variable called 'new' that never gets freed. This is schoolbook example of a memory leak, showing the guy didn't choose C because he's already proficient in it. Or even worse, if he is proficient and the language still allows such serious mistakes to slip through so easily.
Edit: the code is actually completely full of memory leaks the more i read, stuff like else if(dequals(commands.values[0], dcreate(SEARCH))) where dcreate returns a buffer from malloc which would have to be freed.
Yes. I agree so much. Everyone should be free to purchase the car they want. If it sucks gas, the free market takes care of it with gas costs. I pay a ton more in gas tax (priced per gallon) than a smaller car. I also am free to use the suburban for what I want ... long road trips with my family of 5. Towing my boat. Hauling wood. I am also free to park the thing in my garage, because weather permitting (meaning above 10 degrees F) I commute 15 miles each way on my bicycle. My choice. Not anyone else's - including (and especially) the government.
Unheard of ... unless you live in the midwest. Here in Minnesota, a ton of cars have them because a ton of people own boats and/or rv's and/or snow machines. The same reason a lot own all-wheel drive vehicles.
I'm not sure how this works ... 1) husband is sleeping around. 2) wife says "pay me for sex" ... why in the world would a husband whose sleeping around on his wife pay for sex with his wife.
He's probably not sleeping around for free, so $6 might be cheaper.
You might think that sex with his wife was earlier free, but it was happening only when she wasn't mad at him, which was probably not very often.
So either be on your best behavior and occassionally get sex for free, or pay $6 when you want and almost always get sex. Those men probably already chose the second option just with other women and for higher price.
Might work. Also strangely it might bring couples together because having sex with someone just mechanically improves stability of the relationship.
My frustration with automotive controls isn't limited to touch screens, but I've never used a touchscreen I like. I have two cars with awesome controls - a 2000 camary and a 20007 suburban. Both have 3 knobs: 1) how hot/cold 2) how fast is the fan blowing 3) where does it blow. The radio has two nobs - "what channel" and "how loud". My wife's 2013 (?) "luxury" car is quite the opposite. All controls are either 1) buttons you have to press or 2) something on the touchscreen. The user interfaces force you to take your attention from the road to use. That is bad and dangerous design ... end of story. I know the world likes to complain about using phones while driving, the the controls on some cars are just as bad.
