|
Thread Rules
1. This is not a "do my homework for me" thread. If you have specific questions, ask, but don't post an assignment or homework problem and expect an exact solution.
2. No recruiting for your cockamamie projects (you won't replace facebook with 3 dudes you found on the internet and $20)
3. If you can't articulate why a language is bad, don't start slinging shit about it. Just remember that nothing is worse than making CSS IE6 compatible.
4. Use [code] tags to format code blocks. |
On December 19 2018 04:47 bangsholt wrote:Show nested quote +On December 18 2018 19:29 Acrofales wrote:I always wonder that when ppl try to do computation in SQL  I always wonder why people want to transfer data to a client only for the client to filter and sort it. It's almost like a SQL database has WHERE and GROUP BY
I can just take my case from work, I don't have access to the indexed table for data analysis since that is the production server. I only have partial access to a daily BI copy where the only tool I'm allowed to use (Power BI) creates a local copy as part of the data load. Hopefully that changes during next year but doesn't really help now.
Though the actual application doesn't load the full tables into your client. So in the actual use case it works properly.
|
How big is the data set usually? If you don't have more than a few thousand records to compare then performance shouldn't be an issue and it doesn't really matter if your algorithm is O(n^2) or whatever. If data sets are large (hundreds of thousands or millions of records) then it is definitely worth your while to think of a better way of doing things.
|
|
|
Well i stoped watching at 3:27 because he is clearly wrong, at least in practical sense. Yeah sure You can do all the stuff You want on Linux, as long as You are willing (and have time and knowledge) to write all needed drivers and tools. If Your company uses some tool or hardware that has only say windows support, Your options are limited to "use windows", "run Windows on VM and hope it works". If i need to use some dedicated network interface that only has windows support i am not going to rewrite tooling and drivers - i dont have time, knowledge and whats most important i am not being paid to that.
|
On December 20 2018 19:37 Silvanel wrote:
Well i stoped watching at 3:27 because he is clearly wrong, at least in practical sense. Yeah sure You can do all the stuff You want on Linux, as long as You are willing (and have time and knowledge) to write all needed drivers and tools. If Your company uses some tool or hardware that has only say windows support, Your options are limited to "use windows", "run Windows on VM and hope it works". If i need to use some dedicated network interface that only has windows support i am not going to rewrite tooling and drivers - i dont have time, knowledge and whats most important i am not being paid to that.
Then you shouldn't have stopped watching because he clarifies later that if you have to work with proprietary stuff that only works on Windows for example then you should do it. It is a big generalization on his part (he also forgot working with audio professionally, which also lacks tooling for Linux), but really, Linux has gone a very long way in terms of ease-of-use for everyday normal guy.
Also, note that he's speaking at a Linux conference, so people not already doing most if not all of their work on Linux aren't really his target audience 
|
Yeah i am aware of that, maybe i reacted to harshly because i just recently had similiar situation in project. A new architect (not even from my domain) were constantly bugging me with "Why no Linux??, Why no Linux" and my answer was always the same "i am not going to rewrite all the tools and drivers provided by some other parties just so You can have Your dream linux.
BTw: I do use linux on some machines and i like it but i hate when people act like it is some magical solution for every problem.
|
I have a coworker that knows a lot more than me, like different languages, frameworks, different programming paradigms. etc but I can't help to think he's a bad programmer.
His code is almost always buggy. Ideas he bring out and be sure "it will work" never works.
I was trying to track down a silly bug for 3 days, finally solved it, he refactored my code a bit to make it "better", now its more broken than ever :/
pissed
|
On December 21 2018 03:23 mantequilla wrote:
I have a coworker that knows a lot more than me, like different languages, frameworks, different programming paradigms. etc but I can't help to think he's a bad programmer.
His code is almost always buggy. Ideas he bring out and be sure "it will work" never works.
I was trying to track down a silly bug for 3 days, finally solved it, he refactored my code a bit to make it "better", now its more broken than ever :/
pissed
There's a difference between knowing the framowrk and/or language and actually putting this knowledge to good use...
|
On December 21 2018 03:23 mantequilla wrote:
I have a coworker that knows a lot more than me, like different languages, frameworks, different programming paradigms. etc but I can't help to think he's a bad programmer.
His code is almost always buggy. Ideas he bring out and be sure "it will work" never works.
I was trying to track down a silly bug for 3 days, finally solved it, he refactored my code a bit to make it "better", now its more broken than ever :/
pissed
I can relate. I know a similar case, and it is bothering several people. It's a difficult situation and I can't really provide you with solution though... Especially if seniority or personality traits block you from a productive discussion of the issue.
|
|
|
Because Apple does not conform to its own standards and changes them frequently? Some people even claim they deliberately sabotage cross versions compatibility but i think its combination of legitimate reasons (sometimes its better to break compatibility in order to make huge leap) and incompetence.
I experienced it first hand when Daimler decided to drop some functionalities on Apple devices (in old project) because of the mess in Apple standards.
Sry for general ramble instead of helping advice, someone had to say it
|
That's very sad to hear. At work there is a project which has MacOS 10.7 as a deployment target. Managers wouldn't allow me to increase it significantly without a very good reason. Is it possible to support all MacOS from 10.7 to 10.14 (latest) without some random UI problems? For example, I've added a few new buttons which work fine on MacOS 10.14, but on MacOS 10.12 nothing happens when they're clicked.
I'm a Windows user and I find this very weird when I have to maintain Mac projects.
|
On December 21 2018 23:35 SC-Shield wrote:
That's very sad to hear. At work there is a project which has MacOS 10.7 as a deployment target. Managers wouldn't allow me to increase it significantly without a very good reason. Is it possible to support all MacOS from 10.7 to 10.14 (latest) without some random UI problems? For example, I've added a few new buttons which work fine on MacOS 10.14, but on MacOS 10.12 nothing happens when they're clicked.
I'm a Windows user and I find this very weird when I have to maintain Mac projects.
Why do you find that weird? MacOS 10.7 is Lion, and was released in 2010.
If you were to develop something for Windows 10, would you expect it to automatically be backward compatible with Windows 7? Forward compatibilty is a different issue, and generally speaking, software designed for windows 7 is usable in windows 10. Is that not the case for Apple?
|
On December 22 2018 00:13 Acrofales wrote:Show nested quote +On December 21 2018 23:35 SC-Shield wrote:
That's very sad to hear. At work there is a project which has MacOS 10.7 as a deployment target. Managers wouldn't allow me to increase it significantly without a very good reason. Is it possible to support all MacOS from 10.7 to 10.14 (latest) without some random UI problems? For example, I've added a few new buttons which work fine on MacOS 10.14, but on MacOS 10.12 nothing happens when they're clicked.
I'm a Windows user and I find this very weird when I have to maintain Mac projects. Why do you find that weird? MacOS 10.7 is Lion, and was released in 2010. If you were to develop something for Windows 10, would you expect it to automatically be backward compatible with Windows 7? Forward compatibilty is a different issue, and generally speaking, software designed for windows 7 is usable in windows 10. Is that not the case for Apple?
Another thing worthy of note is that if you want to support 10.7 you can't use Swift.
|
On December 22 2018 00:13 Acrofales wrote:Show nested quote +On December 21 2018 23:35 SC-Shield wrote:
That's very sad to hear. At work there is a project which has MacOS 10.7 as a deployment target. Managers wouldn't allow me to increase it significantly without a very good reason. Is it possible to support all MacOS from 10.7 to 10.14 (latest) without some random UI problems? For example, I've added a few new buttons which work fine on MacOS 10.14, but on MacOS 10.12 nothing happens when they're clicked.
I'm a Windows user and I find this very weird when I have to maintain Mac projects. Why do you find that weird? MacOS 10.7 is Lion, and was released in 2010. If you were to develop something for Windows 10, would you expect it to automatically be backward compatible with Windows 7? Forward compatibilty is a different issue, and generally speaking, software designed for windows 7 is usable in windows 10. Is that not the case for Apple?
I know what you mean, but Windows is so much better with keeping things compatible. I've never seen a perfectly normal button work on some Windows, while it doesn't on another Windows version. However, I've seen problems with dependencies on Windows such as Visual C++ Runtime 2015 (merge module). It works fine on Windows 10, but it's totally broken on Windows 8.1 and Windows Server 2012 (I don't understand why some people want to install client software there, but whatever).
Regarding MacOS, deployment target is 10.7, but my development machine has 10.14 (latest) and Xcode 10. When I run software from my machine, it simply works. When another person tests it on 10.12, UI is a mess, no button responds to clicks. I just don't understand how this should be done so it works. Swift isn't used for legacy reasons. Maybe I should use an older Xcode?
|
On December 22 2018 02:14 SC-Shield wrote:Show nested quote +On December 22 2018 00:13 Acrofales wrote:On December 21 2018 23:35 SC-Shield wrote:
That's very sad to hear. At work there is a project which has MacOS 10.7 as a deployment target. Managers wouldn't allow me to increase it significantly without a very good reason. Is it possible to support all MacOS from 10.7 to 10.14 (latest) without some random UI problems? For example, I've added a few new buttons which work fine on MacOS 10.14, but on MacOS 10.12 nothing happens when they're clicked.
I'm a Windows user and I find this very weird when I have to maintain Mac projects. Why do you find that weird? MacOS 10.7 is Lion, and was released in 2010. If you were to develop something for Windows 10, would you expect it to automatically be backward compatible with Windows 7? Forward compatibilty is a different issue, and generally speaking, software designed for windows 7 is usable in windows 10. Is that not the case for Apple? I know what you mean, but Windows is so much better with keeping things compatible. I've never seen a perfectly normal button work on some Windows, while it doesn't on another Windows version. However, I've seen problems with dependencies on Windows such as Visual C++ Runtime 2015 (merge module). It works fine on Windows 10, but it's totally broken on Windows 8.1 and Windows Server 2012 (I don't understand why some people want to install client software there, but whatever). Regarding MacOS, deployment target is 10.7, but my development machine has 10.14 (latest) and Xcode 10. When I run software from my machine, it simply works. When another person tests it on 10.12, UI is a mess, no button responds to clicks. I just don't understand how this should be done so it works. Swift isn't used for legacy reasons. Maybe I should use an older Xcode?
Won't it just auto-update itself though?
Don't know much about Mac development. I couldn't really care less about anything Apple...
|
On December 22 2018 02:36 Manit0u wrote:Show nested quote +On December 22 2018 02:14 SC-Shield wrote:On December 22 2018 00:13 Acrofales wrote:On December 21 2018 23:35 SC-Shield wrote:
That's very sad to hear. At work there is a project which has MacOS 10.7 as a deployment target. Managers wouldn't allow me to increase it significantly without a very good reason. Is it possible to support all MacOS from 10.7 to 10.14 (latest) without some random UI problems? For example, I've added a few new buttons which work fine on MacOS 10.14, but on MacOS 10.12 nothing happens when they're clicked.
I'm a Windows user and I find this very weird when I have to maintain Mac projects. Why do you find that weird? MacOS 10.7 is Lion, and was released in 2010. If you were to develop something for Windows 10, would you expect it to automatically be backward compatible with Windows 7? Forward compatibilty is a different issue, and generally speaking, software designed for windows 7 is usable in windows 10. Is that not the case for Apple? I know what you mean, but Windows is so much better with keeping things compatible. I've never seen a perfectly normal button work on some Windows, while it doesn't on another Windows version. However, I've seen problems with dependencies on Windows such as Visual C++ Runtime 2015 (merge module). It works fine on Windows 10, but it's totally broken on Windows 8.1 and Windows Server 2012 (I don't understand why some people want to install client software there, but whatever). Regarding MacOS, deployment target is 10.7, but my development machine has 10.14 (latest) and Xcode 10. When I run software from my machine, it simply works. When another person tests it on 10.12, UI is a mess, no button responds to clicks. I just don't understand how this should be done so it works. Swift isn't used for legacy reasons. Maybe I should use an older Xcode? Won't it just auto-update itself though? Don't know much about Mac development. I couldn't really care less about anything Apple...
Similar situation here: don't care about Apple. Presumably there's a setting somewhere in xcode that you are developing for a target os 10.7. I've done a fair bit of Android development, and you configure it for a target Android API. It's far from perfect to develop for old versions (keeps complaining about deprecated methods that don't really have a workaround in old versions), but it works. To test you either deploy to a system running that version or you set up an emulator.
|
On December 21 2018 03:23 mantequilla wrote:
I have a coworker that knows a lot more than me, like different languages, frameworks, different programming paradigms. etc but I can't help to think he's a bad programmer.
His code is almost always buggy. Ideas he bring out and be sure "it will work" never works.
I was trying to track down a silly bug for 3 days, finally solved it, he refactored my code a bit to make it "better", now its more broken than ever :/
pissed
I mean, code reviews are a thing?
|
On December 22 2018 04:40 Blisse wrote:Show nested quote +On December 21 2018 03:23 mantequilla wrote:
I have a coworker that knows a lot more than me, like different languages, frameworks, different programming paradigms. etc but I can't help to think he's a bad programmer.
His code is almost always buggy. Ideas he bring out and be sure "it will work" never works.
I was trying to track down a silly bug for 3 days, finally solved it, he refactored my code a bit to make it "better", now its more broken than ever :/
pissed I mean, code reviews are a thing?
In theory, unit tests should have caught that too. 
|
On December 22 2018 04:17 Acrofales wrote:Show nested quote +On December 22 2018 02:36 Manit0u wrote:On December 22 2018 02:14 SC-Shield wrote:On December 22 2018 00:13 Acrofales wrote:On December 21 2018 23:35 SC-Shield wrote:
That's very sad to hear. At work there is a project which has MacOS 10.7 as a deployment target. Managers wouldn't allow me to increase it significantly without a very good reason. Is it possible to support all MacOS from 10.7 to 10.14 (latest) without some random UI problems? For example, I've added a few new buttons which work fine on MacOS 10.14, but on MacOS 10.12 nothing happens when they're clicked.
I'm a Windows user and I find this very weird when I have to maintain Mac projects. Why do you find that weird? MacOS 10.7 is Lion, and was released in 2010. If you were to develop something for Windows 10, would you expect it to automatically be backward compatible with Windows 7? Forward compatibilty is a different issue, and generally speaking, software designed for windows 7 is usable in windows 10. Is that not the case for Apple? I know what you mean, but Windows is so much better with keeping things compatible. I've never seen a perfectly normal button work on some Windows, while it doesn't on another Windows version. However, I've seen problems with dependencies on Windows such as Visual C++ Runtime 2015 (merge module). It works fine on Windows 10, but it's totally broken on Windows 8.1 and Windows Server 2012 (I don't understand why some people want to install client software there, but whatever). Regarding MacOS, deployment target is 10.7, but my development machine has 10.14 (latest) and Xcode 10. When I run software from my machine, it simply works. When another person tests it on 10.12, UI is a mess, no button responds to clicks. I just don't understand how this should be done so it works. Swift isn't used for legacy reasons. Maybe I should use an older Xcode? Won't it just auto-update itself though? Don't know much about Mac development. I couldn't really care less about anything Apple... Similar situation here: don't care about Apple. Presumably there's a setting somewhere in xcode that you are developing for a target os 10.7. I've done a fair bit of Android development, and you configure it for a target Android API. It's far from perfect to develop for old versions (keeps complaining about deprecated methods that don't really have a workaround in old versions), but it works. To test you either deploy to a system running that version or you set up an emulator.
There is indeed. Deployment info is found right below where you set up the app signing.
Developing for iOS has the same problem as android in this regard: There's always new features and functions which requires newer OS versions and phones. Supporting legacy versions is a real pain and honestly not worth it unless you're forced to.
|
|
|
|
|
|
EPT
