Well as I said, context.
What you have listed are options. Assess, then make a call.
However, my dependency chain is calling. Need to make it longer…. :)
- Glav
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Greg Keogh
Sent: Wednesd
Yes that’s correct. We don’t do anything different when you compile for AnyCPU
vs x64 in C# or VB.
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Greg Keogh
Sent: Friday, November 25, 2016 11:13 AM
To: ozDotNet
Subject: Re: Target x86/x64
Old thread, b
>
> "The Only Thing Necessary for the Triumph of Evil is that Good Men Do
> Nothing"
>
Sadly, with JS I think so.
I have some other good news through. Many weeks ago someone in here (I
forget sorry!) mentioned a lightweight ORM named Dapper. I had a need for
something like that last week, and I re
On Sun, Nov 27, 2016 at 9:31 PM, Paul Glavich
wrote:
> Ahh the recurring thread about how immature the JS/Web dev community is
> and how hard it is to do anything “right”.
>
>
>
> All I will say is we asked for it. If we didn’t ask for it, we accepted
> it. If we didn’t accept it, we assumed that
Just choose something and go with it based on your team's experience and
preference. In a few years either the app will be dead anyway or the
employer will have to pay decent money to have "old" devs come and maintain
these "legacy" apps. :p
On Wednesday, 30 November 2016, Greg Keogh wrote:
> ES
ES6
Typescript
AngularJS 1.5
Angular2
Aurelia
Polymer
YARN
NPM
react
grunt
gulp
This list extracted from Glav's message should be a hint that JS is on the
fritz, and it's the tip of the iceberg -- *Greg K*
On 30 November 2016 at 09:13, Paul Glavich
wrote:
> It depends J
>
>
>
> However in an at
It depends :)
However in an attempt to answer, which usually requires a lot more context and
thought, here we go:
* I’d choose ES6/Typescript at a minimum. ES6 imports/modules/classes
are pretty handy and good to separate out your logic. Typescript is also good
for structure/”pre
