If you have suspicion that someone is breaking the Law, have your evidence ready before publicly airing it, and be absolutely prepared to defend your statement when you do.
yeah we'd have to disqualify every republican presidential candidate who has accused obama of breaking the law
good luck making complex queries without having to scan all the records, this is precisely why SQL is better, it can optimize queries so you don't have to scan every record
I will never again be young enough to appreciate 'Speed Racer' or 'Star Trek'. Same is true for Apple ][ games.
I will never be too old to appreciate 'Star Trek' as a valued relic of the era, to appreciate the fact that Spock and Uhura's kiss is not considered risque any more. I will never be too old to appreciate how 'Star Trek' boldly took the racism bull by the horns with the hilarious half-black half-white aliens.
Why not start with a normalized relational database and a language designed to encapsulate and protect data from inadvertent data-entry or programming errors?
nobody actually does this in production systems, if you put in code to detect all possible data input errors, you will not meet any sort of performance goals
you can put in indexes and referential integrity constraints to your heart's content, but then you will find that your INSERT operations are just outrageously slow
it's better in all cases to constrain user input at the application level
The fewer changes there are from the app on your phone to the desktop to the Xbox and so on, the easier it will be for users to discover how to use your app when moving from one device to the next.
that doesn't make any sense at all, the "right" user interface for the job depends on the job, not the overall application. If I am editing text on a phone, I'm not going to be interested in all of the many thousands of options that are available from the deep menu structure of a desktop word processor.
why are people "app" centric? it doesn't make any sense. there is no problem with using different applications on different types of platforms. The elevator does not need to have a steering wheel and pedals, and the car does not need floor buttons. Both are used for transporation, by your logic they should have the same user interface.
there are no significant opportunities for educating younger professionals except through other than "real life" - using live/production systems and actual persons' medical information.
Except NoSQL databases are not guaranteed ACID compliant.
Except when they are:
https://en.wikipedia.org/wiki/Berkeley_DB
"Despite having a simple architecture, Berkeley DB supports many advanced database features such as ACID transactions, fine-grained locking, hot backups and replication."
The more consistent you make your UI between your target device families, the easier it will be for users to approach your application.
totally backwards mentality. TOTAL FAIL.
In fact it is the opposite. It's a pretty fundamental user interface concept. Unfamiliar users do much better when the user interface matches the device being used. If you have a mouse in your hand, you look for the start button or the apple menu. You expect deep menus with lots of functionality, that take dexterity to choose the right item. Much power is at your fingertips. Years and years of drill have pounded this into us.
When you are pointing with a finger, it's different. You don't have the dexterity to choose a single item from a deep complex menu. I could go on and on...
What's the point of developing for a niche platform?
If you are an enterprise and you want to provide a service to your customers, you can do just about everything from the web. You don't need to write an app, you don't need to distribute it and keep it updated. You can write a web app and have everything in one place. You don't have to force your users to upgrade. You don't have to worry about fake versions of your app. You can use web standards and just ignore Microsoft and Apple and everyone else.
The app can easily conform to the size available, similar to responsive websites. (This is nice even on the desktop, because sometimes I'd like my app to work well if I make its window small... so it adjusts accordingly.) Universal apps can easily support various input methods including keyboard, mouse, touchscreen, Xbox controller, and so on.
Who even cares? With miniscule market share, nobody is willing to expend the resources.
The web has expanded its functionality to the point where you don't even need an app for most things. All you need is to surf there in your web browser, phone or desktop.
If you are writing an enterprise app and you think you need a custom client application, you are probably doing it wrong.
I was speaking more from an IT infrastructure point of view. A windows phone with active directory integration and group policy extensions for example. Why this hasn't been attempted yet is a complete mystery. Everyone from small to large business would be all over it.
because your local sys admins have plenty of time on their hands, it's no problem to triple the number of systems they need to administer
Slashdot Mirror
None of the criminals among my circle of family or acquaintences were active or under investigation when I interacted with them.
how do you know this?
If you have suspicion that someone is breaking the Law, have your evidence ready before publicly airing it, and be absolutely prepared to defend your statement when you do.
yeah we'd have to disqualify every republican presidential candidate who has accused obama of breaking the law
good luck making complex queries without having to scan all the records, this is precisely why SQL is better, it can optimize queries so you don't have to scan every record
I will never again be young enough to appreciate 'Speed Racer' or 'Star Trek'. Same is true for Apple ][ games.
I will never be too old to appreciate 'Star Trek' as a valued relic of the era, to appreciate the fact that Spock and Uhura's kiss is not considered risque any more. I will never be too old to appreciate how 'Star Trek' boldly took the racism bull by the horns with the hilarious half-black half-white aliens.
perhaps you might want to actually read the documentation for the current shipping product before you make indefensible statements
Why not start with a normalized relational database and a language designed to encapsulate and protect data from inadvertent data-entry or programming errors?
nobody actually does this in production systems, if you put in code to detect all possible data input errors, you will not meet any sort of performance goals
you can put in indexes and referential integrity constraints to your heart's content, but then you will find that your INSERT operations are just outrageously slow
it's better in all cases to constrain user input at the application level
I meant modern "NoSQL" database engines.
a useless impractical distinction if I ever saw one
BerkeleyDB is thoroughly "modern", could you please list a single attribute that keeps it from being "modern"
a hilarious attempt to back out of your "no true scotsman" statement you ignorantly walked into
>1. I am an American citizen, and I have the right to enter my country.
citation required
BerkeleyDB IS a NoSQL database
Just because it existed before the word NoSQL doesn't mean it isn't one
BerkeleyDB is most certainly a database, it comes with an executable program that can be used as a full-featured database.
And no, there isn't currently a NoSQL DB that is ACID compliant.
Isn't that funny? The very product mentioned in this article (Intersystems Caché) is a NoSQL DB that is ACID compliant.
At least then you could add means to import and export objects with JSON or something like that.
since when do you need an IDL to work with JSON?
The fewer changes there are from the app on your phone to the desktop to the Xbox and so on, the easier it will be for users to discover how to use your app when moving from one device to the next.
that doesn't make any sense at all, the "right" user interface for the job depends on the job, not the overall application. If I am editing text on a phone, I'm not going to be interested in all of the many thousands of options that are available from the deep menu structure of a desktop word processor.
why are people "app" centric? it doesn't make any sense. there is no problem with using different applications on different types of platforms. The elevator does not need to have a steering wheel and pedals, and the car does not need floor buttons. Both are used for transporation, by your logic they should have the same user interface.
there are no significant opportunities for educating younger professionals except through other than "real life" - using live/production systems and actual persons' medical information.
the nonsense is STRONG in this one
I've read about MUMPS, never programmed in it,
you could have stopped right there, everything after it is nonsense
Except NoSQL databases are not guaranteed ACID compliant.
Except when they are:
https://en.wikipedia.org/wiki/Berkeley_DB
"Despite having a simple architecture, Berkeley DB supports many advanced database features such as ACID transactions, fine-grained locking, hot backups and replication."
The more consistent you make your UI between your target device families, the easier it will be for users to approach your application.
totally backwards mentality. TOTAL FAIL.
In fact it is the opposite. It's a pretty fundamental user interface concept. Unfamiliar users do much better when the user interface matches the device being used. If you have a mouse in your hand, you look for the start button or the apple menu. You expect deep menus with lots of functionality, that take dexterity to choose the right item. Much power is at your fingertips. Years and years of drill have pounded this into us.
When you are pointing with a finger, it's different. You don't have the dexterity to choose a single item from a deep complex menu. I could go on and on...
the best tablet for doodling and audio editing out there.
Gosh I gotta go out and buy one now, so I can doodle better!
What's the point of developing for a niche platform?
If you are an enterprise and you want to provide a service to your customers, you can do just about everything from the web. You don't need to write an app, you don't need to distribute it and keep it updated. You can write a web app and have everything in one place. You don't have to force your users to upgrade. You don't have to worry about fake versions of your app. You can use web standards and just ignore Microsoft and Apple and everyone else.
The app can easily conform to the size available, similar to responsive websites. (This is nice even on the desktop, because sometimes I'd like my app to work well if I make its window small... so it adjusts accordingly.) Universal apps can easily support various input methods including keyboard, mouse, touchscreen, Xbox controller, and so on.
Who even cares? With miniscule market share, nobody is willing to expend the resources.
The web has expanded its functionality to the point where you don't even need an app for most things. All you need is to surf there in your web browser, phone or desktop.
If you are writing an enterprise app and you think you need a custom client application, you are probably doing it wrong.
I was speaking more from an IT infrastructure point of view. A windows phone with active directory integration and group policy extensions for example. Why this hasn't been attempted yet is a complete mystery. Everyone from small to large business would be all over it.
because your local sys admins have plenty of time on their hands, it's no problem to triple the number of systems they need to administer
even if they have to do it themselves
Translation: We don't want to work with our hardware partners any more.
Why should Dell, Acer, HP, etc. continue to do business with Microsoft when Microsoft openly says that they are going to compete with them?
How can these companies compete with Microsoft in the Windows market? They can't. They will realize this...
Way too many people are rooting for one side or the other, as if these are sports teams. Both sides are idiots.
if both sides are idiots then it is even more important that they agree to not be idiots. Where else can you start?
what do you plan to offer the iranians that they will accept?
which president hung a banner stating "mission accomplished"? just asking
What terms would you be able to convince the Iranians to agree to?
what can you get the iranians to agree to?