|
Oh hell no
Someone's therapist knows all about you!
|
|
|
|
|
|
Might need to inflate the tires on my bike. Pedal on over to the bar.
|
|
|
|
|
Are they cheering at the end because he is still alive?
|
|
|
|
|
Me and My Shadow
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Jörgen Andersson wrote: At least I hope he wears a helmet.
And a parachute in case he goes off the edge?
|
|
|
|
|
The way I drive, a helmet cam would be very useful...
|
|
|
|
|
That's some talent, and a whole lot of no fear.
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
|
|
|
|
|
I was getting caught up on my Dilbert daily desk calendar and saw this one, Dilbert Comic Strip on 2014-07-15 | Dilbert by Scott Adams[^]
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
That can be done. No big deal.
P.S. Now I'm reminded of "blip-verts" in Max Headroom.
|
|
|
|
|
So highly advanced even that after 24 years of HTML and who knows how many versions and framework after framework and the second full installment of Angular that is developed and supported by one of the biggest tech companies in the world with the first major update A FRIGGIN DATE INPUT STILL DOESN'T WORK!!!   
So I'm doing a simple web site using Angular 4.
The following just does not work.
<input type="date" [(ngModel)]="myDate" /> And in my TypeScript:
this.myDate = someInitialDate; This is pretty basic stuff if you ask me
I've been looking for a fix for over an hour, but I've come across sketchy solutions that seem to work until you enter some value manually.
It seems the only solution is to use some third party date input control.
If I knew how to import one using .NET Core, npm, WebPack, TypeScript and Angular imports...
Sounds easy, but it gets downloaded to node_modules/some_datepicker, but also needs node_modules/something_else, it's all in TypeScript, I need to move it using WebPack because node_modules isn't public, but WebPack makes bundles, so I'd lose my single file, which I need in the TypeScript import to register it in Angular... 
I miss WinForms! 
|
|
|
|
|
Look at that: the tool chain that made me drop Angular like a bad habit.
Enjoy the hipster stuff!
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Yeah, that's front-end development in 2017 I guess... 
|
|
|
|
|
It's the noisiest part of it. I don't know, it's as if increasingly interdependent tool chains have become a status symbol of sorts. It's a pity, because Angular 1 is absolutely fantastic, as are a lot of the first generation frameworks that we've seen, but as they become an "industry standard" the developers begin losing their minds.
I'm beginning to suspect that this is happening because so much of the open source monetization strategy is rooted in training.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
|
Angular! Say no more! To be fair most web stuff is crap... It's not their fault, developing interacting app on stuff that only render text almost like one want is not that easy...
Anyway try that: Vue.js you might be pleasantly surprised! 
|
|
|
|
|
Super Lloyd wrote: Anyway try that: Vue.js you might be pleasantly surprised!
Yep, the best way to solve the internet issues is to focus on the next Framework.
Paulo Gomes
Measuring programming progress by lines of code is like measuring aircraft building progress by weight.
—Bill Gates
Everything should be made as simple as possible, but not simpler.
—Albert Einstein
|
|
|
|
|
Yeah, I've heard good things about Vue.js.
I actually recommended it to a coworker who wanted to introduce some JS framework in a fairly complicated and existing project.
I mainly chose Angular because I'm expecting my software to become more complicated.
And because businesses want Angular and it's a good learning experience.
|
|
|
|
|
I dunno about Angular 2, but Angular 1 is needlessly complicated...
The end results is that you have bugs and issue in relatively common component that are left unfixed for quite a long time...
I get if the business wants it well you probably can't do much about it and just suck it up and move on.
Anyway, just to I told you so, I would argue the following. What does AngularJS bring that is worth?
- MVVM. VueJS does it much better, simpler and better performance
- Auto downloading of component (HTML) template and related component's javascript. Ok this one is nice. Probably can be written from scratch without too much effort or replicated with requirejs, or maybe bundle everything ASP.NET MVC style
- dependency injection. While this is a nice technical achievement it's not that big a deal.
And then what Angular drag you down with: Complexity, foloows by long standing bug in main components....
|
|
|
|
|
Yeah, you may have convinced me...
Angular 4 is a drag. I've lost two nights trying to get that friggin' datepicker to work.
I'm not a big fan of TypeScript either, appears I favor less typing over type safety in JavaScript.
I'll have a look at ReactJS as well.
|
|
|
|
|
nice! Yeah I had problem in Angular with a datetime picker too, haha.
I quite like TypeScript, I thought it really doesn't constrain me much at all. But if it does bother you occasionally just make your variable any type. If it bother you often drop it. But I am surprised that it does... Although if you are the one that brings it to the company I could understand that you have learning curve issues.... godspeed!
|
|
|
|
|
Quote: So I'm doing a simple web site using Angular 4
If it's a simple website, why use Angular at all? Sledgehammes and nuts, and all that....
|
|
|
|
|
I'm expecting the app to grow bigger
Besides, it's a nice learning experience!
|
|
|
|
|
Come back to WinForms.
(We all float down here.)
|
|
|
|
|
PIEBALDconsult wrote: Come back to WinForms.
Yes, with winforms, at least all the bad stuff is _known_! 
That's why we (older) devs really love winforms. Because, when we were using winforms we were complaining about winforms too. As a matter of fact, I (and I'm not kidding) submitted a bug on the Date/Calendar control for WinForms.
EDIT - It's MonthCalendar control - couldn't remember name of that thing.
Here's how it went.
WinForm DatePicker Bug (undocumented feature)
When my winform was sitting there doing nothing, I found out an event was being fired every 15 seconds.
As I investigated I discovered (an undocumented feature) a bug where the Calendar datepicker in WINFORMS! actually created a timer that would run the OnDateChanged() event every 15 seconds.
The crazy thing was that it wasn't really OnDateChanged() because the date hadn't changed.
But think about this ===> What if the winform app is running and the date changes?
Well, that means the little icon that you can click that takes you to "Today" would be incorrect.
EDIT 3 -- Found an old report of this problem (MonthCalendar -> automatic execution of dateChanged event-VBForums[^])
So the Microsoft control devs, went ahead and added a timer (unbeknownst to most devs) that would run every 15 120 seconds in an effort to determine if the date had changed. However, that would be okay, if it were the :
OnCHECKForChangedDate() event, but it wasn't. That meant that even though the date did not change my code for DateChanged() would run.
EDIT 2 -- looks like they have fixed it now...well, 8 years ago!! 
It was quite terrible and on WinForms DatePicker().
It's still there too. I had to then check if the date had actually changed. Alas.
Alas...
Winforms bit us often too. 
modified 1-Nov-17 17:13pm.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
