|
Message Removed
modified 3-Jun-15 19:05pm.
|
|
|
|
|
Message Removed
modified 3-Jun-15 19:05pm.
|
|
|
|
|
I've been less active here for a while - the reason is the place where I work is migrating from flash to an HTML5/CSS/JS stack (specifically angular). All fine.
My job has been extended to include training grads -so I've been more or less using this stack for 8 months now. One thing became clear - the stack is not kind to windows users. Some of the packages don't seem to have been tested properly, but also the file-watcher in the OS is sub-par, and we use those a lot. I tried to save myself by using a linux VM, but performance was poor and the solution did not work at all.
I'm not going to sugar the pill: Gentleman, I'm migrating to a Mac*
I feel so ashamed and dirty - and not in the usual, good way. I'm off for a little weep now, and to see if I can grow a moustache.
- Work is paying for it, obviously.
|
|
|
|
|
It was nice to know you. I wish you all the best in your future life. Just put the keys on the entrance cabinet when leaving.
|
|
|
|
|
Quote: Just put the keys on the entrance cabinet when leaving
And don't expect any refund of your CP subscription! 
How do we preserve the wisdom men will need,
when their violent passions are spent?
- The Lost Horizon
|
|
|
|
|
Do you still have to listen to Radio 1 too?
|
|
|
|
|
Oh that stopped ages ago. Someone managed to convince senior management that putting your development team inside a call-centre is not a productive move.
|
|
|
|
|
|
We once had an onsite dev-team working within a call centre and in it's defence I have to say that no-one ever went without a fu date should he want one.
veni bibi saltavi
|
|
|
|
|
Nagy Vilmos wrote: no-one ever went without a fu date should he want one.
Is this CP (taxi cab) confidential? 
Once you lose your pride the rest is easy.
In the end, only three things matter: how much you loved, how gently you lived, and how gracefully you let go of things not meant for you. – Buddha
|
|
|
|
|
You are just somebody I used to know, from now! 
|
|
|
|
|
Keith Barrow wrote: to see if I can grow a moustache soul patch
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Just tried to imagine Kate Winslett with a moustache.
Mind bleach anyone?
|
|
|
|
|
Is she doing a handstand?
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
Thanks, now I don't need the bleach anymore.
|
|
|
|
|
Keith Barrow wrote: I'm migratingupgrading to a Mac
PooperPig - Coming Soon
|
|
|
|
|
At some point in every man's life (sometimes women too), they come to a cross-roads. At this cross-roads a decision has to be made. How will I grow my moustache?
http://en.wikipedia.org/wiki/Moustache[^]
|
|
|
|
|
I now have to grow a 'tache so I can get me a moustache spoon - Kool Factor Nine!
veni bibi saltavi
|
|
|
|
|
I wish my work would pay me to grow a moustache... 
It was broke, so I fixed it.
|
|
|
|
|
Keith Barrow wrote: the file-watcher in the OS is sub-par
Okay, as soon as I attempt to discuss this, someone is going to call me a Windows FanBoi or something, but I would like to explain.
Are you talking about the FileSystemWatcher (FSW)?
If you are I originally thought there were issues too.
However, what I learned is that I didn't understand what the File System itself does.
I wrote a program that allows you to watch all file events (Changed, Created, Deleted, Renamed ) on any particular drive and then exclude any paths you want as it runs.
Anyways, while writing that program I learned that what people think is "wrong" is
When a file is copied to a directory, the OS/file system gives it a temp name so whenever you copy a file to a directory you actually get more events than you expect.
You get something like:*
1. file created (with temp file name)
2. file renamed (to the target name you know the file as)
3. file created (then another file created as the file name you know it as)
* - It's been a while so I forget the exact file system events.
My point here is that every dev I know says that the FSW is broken and records multiple entries for one file, but that is because they don't understand the File System / OS and what it does.
Again, not trying to defend FSW or OS or whatever, but thought this might be interesting.
|
|
|
|
|
newton.saber wrote: but thought this might be interesting.
It is.
The difficulty I'm having is with a node (actually grunt + gulp related framework) task - add a file and it doesn't pick it up. I guess the above is the problem.
|
|
|
|
|
Ah, grunt, I've had similar problems. As a matter of fact I ended up writing my own program to LiveReload my web page when there was a change.
You know, during development you are making changes in your HTM or JavaScript and you want your browser to reflect the changes automatically so you don't have to keep doing a refresh?
I wrote up the project as a CP article and it uses the FSW:
WebRefreshR - LiveReload All Your Browsers Easier (WebDevs Unite!)[^]
|
|
|
|
|
Welcome back; glad to hear from ye, Keith, and congratulations-and-deepest-sympathies on your new work challenges.
It would interest me to know more about with-what/where-in (in Angular ? ... the "HTML5/CSS/JS stack" ?) you find issues with Windows. I am currently thinking that it's time I dip a toe into those shark-filled waters, and Angular is the flavor or choice, at the moment. But, I'm not sure if that will be Angular as-is, or Angular 2.0 always-on-the-horizon.
cheers, Bill
«I want to stay as close to the edge as I can without going over. Out on the edge you see all kinds of things you can't see from the center» Kurt Vonnegut.
|
|
|
|
|
BillWoodruff wrote: HTML5/CSS/JS stack.....Angular
Nowhere there specifically - it's actually the build tooling we use: node and (especially) gulp.
Most of it isn't properly tested on Windows - I guess it's written by people on the exact environment whose name I dare not utter here. Specifically:
0. The Build is much slower on a similar spec name - the linters on the Win box take longer than m'colleagues whole build
1. The node environment blitzes the machine - 100% CPU, 100%time serving web pages
2. The command line has huge buffer issues - Iost a full day's effort fixing a unit test. The failure result I kept getting was actually from the first run, but kept showing up in subsequent runs.
3. File Watcher - the environment is mostly build & let the file watcher update - under windows it doesn't look like a new file is added to the watch, meaning a re-build. Not a biggie, but occasionally catches me out.
|
|
|
|
|
I look forward to seeing your Mac based articles. We need more of those.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
